Open roamye opened 3 months ago
-1 on this issue -- I don't think special collections should be treated as archives. #agenda
@azaroth42 - I have added this to next weeks agenda (08-02)
From IT Team Meeting 08/02: Special Collections should be treated like departmental collections. Treating it as so will remove the ability to add the breadcrumb link (intentional). However, this issue is a bigger topic to discuss with interactions at the next Interactions Meeting.
Questions for interactions:
I believe the requirement is to offer the ability to show a subset of items that are part of a named collection set (eg. Garvan Collection or the Leonard S. Marcus Collection of Children's Literature). These named collections are neither archives nor are they departmental collections. The UI for the set needs to show that the collection is part of departmental collection via the breadcrumb. The UI for objects also needs to show the breadcrumb.
Responsible unit > Departmental Collection > Set Name
There may be a secondary requirement that the departmental collection or responsible unit page have some way listing sets, eg. the Beinecke page: https://lux-byunit1.collections.yale.edu/view/set/feb70d01-0cfc-4c01-a643-5eec58b311b6 should list Leonard S. Marcus Collection of Children's Literature somewow.
I do know not know what the question is for Interactions, although we could make sure there is consensus about this approach. It seems like a data question - can the units that have these sets identify them as such in a way that the FE can idenitfy them?
No breadcrumbs (pointless as they're only one level deep).
Instead should be like a department collection, just not managed by a department. e.g. should have the search list for included objects at the top, not explore at the bottom, and no hierarchy for the items within it
This may be blocked by https://git.yale.edu/LUX/unit-data/issues/147
Problem Description: Objects in special collection sets need to display a breadcrumb hierarchy. However, since special collections are not archival sets it does not currently display this breadcrumb as archival sets do.
Expected Behavior/Solution:
Requirements:
Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.
UAT/LUX Examples:
Dependencies/Blocks:
Related Github Issues:
Related links:
Wireframe/Mockup: