Overview
The admin interface for our CMS controls a number of disparate functions, from user management to metadata assignment. Admin is an all-or-nothing permission, currently held by two staff members: Megan Forbes and Jesse Martinez. Jesse is not a regular end-user of the system; rather, he is responsible for system maintenance, upgrades, fixes - anything that requires getting into the code. Megan is responsible for everything else described below.
System Administration
Contains two logs, the event log and task queue log. The event logs contains logs for debugging, errors, logins, and login failures. The task queue log contains logs for the media processing queue.
Use: Never
Notes:
- Never used not necessarily because it's not useful, but because system administration/oversight is somewhat lacking at the moment given the time constraints of the system administrator
Screenshots:
Event log
Task queue log
Access Administration
Contains interfaces for user login management and user role management.
Use: Frequent
Notes:
- Although there is an interface for user role creation, it is not possible for the sysadmin to assign permission to newly created roles, rendering the functionality more-or-less non functional.
- There are no definitions for existing roles.
- The admin may inactive users while maintaining their accounts, which is useful.
Screenshots:
New user
Role list
Role detail
Objects Administration
Contains a large number of user interfaces for classification, metadata, custom fields, and relationship types.
Attributes
User interface for assigning specific attribute fields to a particular artifact class or work type. A default set of fields may also be established.
Use: Often
Screenshots:
Attribute assignment
Object types
User interface for adding items to the Museum's bi-level classification system (Artifact classes and Work types). New terms may be added, terms may be reordered, moved under new headers, etc.
Use: Often
Screenshots:
Object type list
Object type detail
History types
User interface for adding additional categories to the "history" tab in Cataloging. Each category (e.g. storage location) includes the same set of data entry fields (free text and a date).
Use: Rarely
Screenshots:
History example: Storage
History type list
History type detail
Number types
User interface for adding new terms to the controlled list in the "numbering" tab in Cataloging.
Use: Rarely
Screenshots:
Number types
Object doc. types
User interface for adding new terms to the controlled list in the "docs" tab in Cataloging.
Use: Never
Screenshots:
Object doc types
