These are chat archives for collectiveaccess/support

1st
Jul 2017
Axel
@axel20000
Jul 01 2017 00:30
Hello. I need advice at something. A museum wants to use collective access to store its catalogs. Unfortunately they find Providence's UI kind of difficult to find places to manage certain things and create/update catalogs is found difficult for them. I think I have 2 options: 1) Tweak Providence's UI to make it more friendly. 2) Create a separate project which would use Providence's API to query, create and update catalogs. I think option 1) is better but I don't know if Providence is designed to be tweaked and still be able to be updated with future versions of CA. Also the learning curve for both approaches is important. What do you think is the best option??
sterlingjenson
@sterlingjenson
Jul 01 2017 17:59
@axel20000 What specifically are the finding problematic to manage with the UI? I am wondering if the situation is simply not being familiar with the software.
Axel
@axel20000
Jul 01 2017 19:06

That's a good question. We asked for specification about what they wanted to improve. They said that filling out the form to create/update objects was expected to be "easier to use". We think that probably Providence's terminology can be a reason, because it uses standard terms like "object", "entity", etc. They probably use another language for similar things. Of course the last thing is speculation from us, but if we're right, I think its easier to change some terms and probably organize menu access in a different way to make it easier for them to understand and have some key functions accessible straightforward. At first I found myself confused with menu access so I think that can be part of the problem. I think create/update objects is not that difficult but they said that they wanted to create contents "easier", so I guess we can make some improvement on Providence (if that's possible).

At the end, I think most of the situation has to do with being familiar with the software, but some UX tweaks can help them feel "better".

sterlingjenson
@sterlingjenson
Jul 01 2017 19:34
One step I did not do as well as I should have when first setting up Providence is trying out different installation profiles.
Axel
@axel20000
Jul 01 2017 19:37
Do "installation profiles" allow to show forms / menus in a different way to certain users?? Probably some forms can seem complex to users and some way to alter what these users see on forms can help a lot
For example if Providence has a specific file for forms layouts and if its architecture considers that I can tweak some layouts a little.
sterlingjenson
@sterlingjenson
Jul 01 2017 19:43
I just checked, on the user interface setup pages (under administration), you can restrict it by group or user.
I brought up installation profiles because if the group uses a specific set of terminology perhaps one of the other profiles might fit that nomenclature better. As an example, if everyone is used to using VRA core, then the Dublin Core installation profile would not be a good fit
Axel
@axel20000
Jul 01 2017 20:03
I need to check for "installation profiles" then. I checked groups and they're fine to set cataloger but can't modify what the group can see (as far as I checked).
I think the museum will use something based on Dublin Core, but just as reference. At the end they'll probably use their own terminology, but as I understand you, an "installation profile" can be modified to use the terminology they will finally use