This document is broken into the following sections: Disable, Hierarchies, Titles & Ids, Search, Feature Settings, Access Control, Styling, Mapping, System Defaults, Media, Admin Configuration and Export. WHEN TO CUSTOMIZE: App.conf handles most customizations that are not controlled through the UI or profile (with the notable exceptions of: browse, id number configurations, and additional settings for dates, media and search). WHAT: This is the main application configuration file for Providence, designed so that users can easy manage various system-wide settings in one convenient location. nf and the search section) the app.conf section controls only high-level options, while the file handles detailed configuration. For sections where a separate configuration file is also available (Eg. To make editing app.conf a bit more manageable the file is broken up into several sections grouping related options: menus, disable switches, hierarchies, titles and identifiers, search, features, access control, styling, mapping, defaults, media, administration and esoterica (things you probably won’t ever need to change). General configuration of CollectiveAccess is controlled by the app.conf configuration file. Proxy server configuration for web services ID numbering (for objects, object lots and authorities) URL configuration (paths to controllers and themes) Restrict editing of codes for list and metadata elementsįile names for data export download files System configuration check options (under “Manage” > “Administrate” > “Configuration Check”) Task queue set up (deferred processing of uploaded media)Ĭharacter set to use (usually utf-8 might be ISO-8859-1) ca_entities, ca_occurrences, etc.)ĭefault template for media viewer captionĭefault to summary when opening item for editing? Site page templates (Pawtucket content management)ĭefault bundle display templates for related bundles (Eg. Global template values (Pawtucket content management) wysiwyg) editor optionsĮnable dependent field visibility feature Quicksearch - order and results (“live” search in search box in header)Ĭaption formatting for search/browse “thumbnail” results Require preferred label value be present in a listĪllow automated renumbering objects with lot idno + sequence number? Require input id number value to conform to format? (0=no, 1=yes) Show/Hide child records in search/browse resultsĮnable display of collections and objects as a single hierarchy Show/Hide hierarchy root (Storage Locations & Places) (And I should know: I usually seem to be the one who ends up having to process it.Show “add child record” control in editor inspector?Ĭollection hierarchies on the Summary screen Inconsistent data is garbage which requires hours of human intervention every time it has to be processed. Consistent data can be translated and migrated automatically from one format to another. I'd say it's more important that you pick a format and then stick to it consistently. To be honest it shouldn't matter how you choose to store the information so long as it works for you at the time and so long as you document your decisions so that future users can migrate the metadata to a new format in future if the need arises. This format does forbid that individual tag values contain spaces or forward-slashes, but I believe tags should be compact and unique tokens with a defined meaning, not verbose free text, so this constraint should not be a problem. So when I mark an image with the "Brighton" sub-tag which is nested under the "East-Sussex" sub-tag, nested under the "UK" sub-tag, nested under the "located" top-level tag, and also the "Friends" sub-tag nested under the "populated" top-level tag, digiKam adds this to the TagsList field: populated/Friends, located/UK/East-Sussex/Brighton Well you can find a list of XMP field names used by common photo software on this page.įor example, digiKam uses the TagsList field name in XMP metadata to store its tag hierarchy.
0 Comments
Leave a Reply. |