Page Comparison

Seamless integration with 3rd party platforms/systems, including intuitive, streamlined requesting via Aeon, and integration with other systems (ArchivesSpace/OAC, Calisphere, eScholarship, Archive-It, local digital libraries)

JMJ

 A backend for purchases/acquisition module that is less opaque

JMJ

Special collections materials are more easily accessible and discoverable for non-experienced special collection users → increasing ranking of special collection materials in searches, clearly identifying materials as being from special collections, faceting by special collection materials/repository

JMJ

Clear holdings information about where a collection is held, especially in case of UCs with multiple special collection units, with unit-specific notes clearly viewable; ability to differentiate between different campus libraries and campuses

JMJ

 Index fields used by special collections catalogers and for instruction and reference of special collections materials instead of making them staff-only (e.g. at UCLA -- 563 field)

JMJ

Citation lists from searches that could be output as text or PDF

JMJ

Ability to note access issues for specific item records in consistent way and ensure this information is transparent to users

JMJ

I feel like this can be defined in system-wide descriptive guidelines/practices and are not necessarily going to be system-driven. Unless we mean ensuring that the display in Primo is coded in a very transparent way to denote access issues. – Jasmine

Ability to restrict targeted item records from requesting in a collection that is generally open for research

JMJ

Simplification of the cataloging workflow; less duplication of efforts to get records into our system and from/into OCLC

JMJ

 Retention of and ability to search, view, and differentiate local fields 

JMJ

Consistent language to distinguish SCA materials that are digital/digitized but not accessible online

JMJ

Also something that can be defined in system-wide descriptive guidelines/practices. – Jasmine