![]() The type hierarchy behavior can be independently for each type of hierarchical record. When disabled, all types are allowed anywhere. Of type “Page”, “Figure” or Frontspiece sub-records of a “Page” may be only of type “Figure.” In the example above, the sub-records of a “book” can be Type below the top-level type, not just direct sub-types. We partially enabled, top-level records may only be created with top-level types, but sub-records may be of any ![]() … then top-level records can only be of type “Book.” Sub-records of books may only be “Page” or “Frontspiece” Īnd sub-records of “Page” can be “Figure.” “Frontspiece” may not take sub-records. If you have an object type hierarchy like this: Book Page Figure This ensures conformance with the type hierarchy. With types that are direct sub-types of the parent’s type. When fully enabled, top-level records may only be created with top-level types, and sub-records may only be created 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) Show “add child record” control in editor inspector?Ĭollection hierarchies on the Summary screen ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |