These are chat archives for collectiveaccess/support

23rd
Mar 2016
mrjayviper
@mrjayviper
Mar 23 2016 00:31
@stefankeidel so I can change the label via UI. but it seems it's not possible to change the tooltip for hardcoded elements? thanks again
jessica-s
@jessica-s
Mar 23 2016 01:16
Hi there, another front-end user question regarding user access levels on Providence. Hoping I can articulate this clearly ! It seems that in the 'Cataloguer' role cannot you add new related items via Object Screens (is this Quick add?). I had got used to that function on our test server when I had an admin role (e.g. http://imgur.com/cx6tsX7). Is there a good reason for blocking that function for cataloguers? It means the cataloguer must leave the Object page and add a New Entity / New Place / New Procedure etc, then going back into the individual object record and add that related item in. Ideally we would like flexible access for the 2 Collections Managers (to input data as needed) and read-only access for other staff in our museum. I assumed that would mean 2x cataloguers access and then general access for the rest of the staff. But should it be 2x 'Administrators' instead? The issue is that even with the collections managers I want there to be as little chance of compromising data as possible, so worried that as Administrators we may have too much access... if someone is able to clarify that would be fab :smile:
mrjayviper
@mrjayviper
Mar 23 2016 01:19
Hi again. what are user groups? I looked at the wiki and on actual settings and it seems there's not much there. And most of the actual rights are on role. Thanks!
Kehan Harman
@kehh
Mar 23 2016 02:57
@jessica-s I'd recommend that you keep their role to Cataloguers, and just enable quick add for the specific types of records that you want them to be able to add. You can configure the permission for quick add for cataloguers through Manage > Access Control > Access Roles > Cataloguers > Actions > [Table name] editing > Quick add [table name]. Or even define your own Collection Manager role that has this permission.
You'll have to define the access control through an admin role though
Kehan Harman
@kehh
Mar 23 2016 03:04
@mrjayviper You should be able to add a Description and an Add Label through the UI editor which will come up as a tooltip (see https://github.com/collectiveaccess/providence/blob/master-fix/app/models/ca_editor_ui_bundle_placements.php#L41-L64 for these available settings on bundle placements). You might have to add the bundle, save the form and then change these values after the save (I remember an issue where you couldn't edit these fields directly after dragging a placement). (or was that a feature ;) )
jessica-s
@jessica-s
Mar 23 2016 03:18
OK makes sense. Thanks @kehh much appreciated
mrjayviper
@mrjayviper
Mar 23 2016 04:07
thanks @kehh works! :)
mrjayviper
@mrjayviper
Mar 23 2016 04:15
hi again. sometimes there's a quick add pop-up that sometimes appear when wanting to enter new data (open existing object => relationships => enter new entry in related places). I want to modify this pop-up. mainly removing the locale setting. but I looked at the metadata elements and I cannot see anything related. Is this something we can edit? thanks again
jessica-s
@jessica-s
Mar 23 2016 05:20
hi @juliaweist, just picking our conversation from March 10. You mentioned its better to use only one or the other procedure for Condition (e.g. remove the condition page from procedures and only use the condition screen within Object screen or vice versa). We are in the process of tidying up the screens on Providence and working out what is best for our workflow and have come across this issue again for audit, valuation, conservation - they all appear as individual fields within Object > Condition and Object > Valuation, but they are also under New > Procedure > Audit for example. You said several of your museum users take the standalone approach. I feel the inputting from the procedures menu makes sense, especially from a reporting/display point of view, but can't get my head around why it would be useful to use it within the object editor when the containers become so complex and require more playing around with templating when it comes to pulling up a report. Do you have any examples of users using the other approach e.g. condition/audit/valuation functions within the object editor, and how the condition boxes look? All of the data inputed into condition, conservation, audit & valuation will be entered multiple times over the years for an individual object so feel like this gets messy/hard to navigate within the individual object page. Same goes with artwork movements, but I understand this is still a work in progress for the CA team?
mrjayviper
@mrjayviper
Mar 23 2016 06:00
@stefankeidel So I followed your suggestion in regards to clearing app/tmp which I've done via caUtils clear-cache. But the locale settings for this particular container (1 container with 2 text fields) is still showing even after I logged out. Any more ideas?
Also I noticed that the locale issue is NOT present when the text is by itself and NOT inside a container.
is there a "hack" way (e.g. writing into the DB directly via an update SQL) to disable all locale settings for all text fields? thanks again
Stefan
@stefankeidel
Mar 23 2016 12:22
@mrjayviper no, not really
are you sure the caUtils clear-cache worked? more often than not the cache files are owned by the web server user and so if you run the script with a normal user account, it might not be able to kill everything
try removing app/tmp/collectiveaccessCache by hand
it should kill all existing sessions when you do that, i.e. when you try to navigate to the next screen in the UI, you should get logged out
For the locale settings, have you tried just disabling whatever second locale you have enabled for cataloguing? You can do that under Manage > Administration > Locales. There's a checkbox "enable for cataloguing" or something like that
Julia
@juliaweist
Mar 23 2016 16:53
Hi @jessica-s we just developed a feature that helps with this (complex containers that repeat many times). It's a setting on the container attribute called readonlyTemplate. Some info here: http://docs.collectiveaccess.org/wiki/Attribute_settings:_Container. Essentially it allows you to program a display with a click to edit button so that the data is more readable.
mrjayviper
@mrjayviper
Mar 23 2016 23:25
@stefankeidel Hi again. I believe "caUtils clear-cache" worked. app/tmp was empty after running it. I run the command as root since I don't know the apache login. I'll check that setting. it might just make it universal. Thanks! :)
mrjayviper
@mrjayviper
Mar 23 2016 23:36
@stefankeidel changing that setting worked! thanks a lot :)
Stefan
@stefankeidel
Mar 23 2016 23:36
Yay!
mrjayviper
@mrjayviper
Mar 23 2016 23:45
another question, is it possible to remove fields from the "quick add" pop-up? I have a request here to simplify it a bit. or perhaps this is universal and removing stuff would messed up other sections?
Stefan
@stefankeidel
Mar 23 2016 23:47
The quick add just takes the first screen of whatever user interface that user has selected under Manage > My Preferences > Quick Add. You could make a separate UI for quickadd and then have people select it there. That way it wouldn't interfere with the main editor UI configuration for that record type
Or you could move bundles off the first screen to other tabs and keep it all in one UI -- whatever is easier
mrjayviper
@mrjayviper
Mar 23 2016 23:59
seems leaving quick add as in is easier though...