You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition, within the record itself, its format is given as "Manuscript, Book" (and very prominently, I might add). But neither is accurate, and users who use the "Visual Material" facet also lose this item from their results list, even though that is the most logical format option for a single photograph.
The text was updated successfully, but these errors were encountered:
Why would ArchivesSpace records export as books? Should the default export from ASpace be some form of archival materials? Also, why would it export as an "Online" resource if there is no online component?
Separately- if something is specifically Graphic Materials, could we get it exported to the catalog as Visual Materials so that facet can be activated?
The "Online" badge is created because the record has an 856. For archival records, that's the finding aid link. Ind2 "2" means it's a "related resource" (not the resource itself). Is there a way to exclude those records from the badge creation? See this ticket.
"Manuscript, Book" comes from the hardcoded "mixed materials" in the ao exporter. That can be addressed by giving HM new specs. See this ticket.
From Molly via Lexy:
When you search in the catalog for the example below, it comes up as an "Online" resource. This would lead users to believe it's been digitized.
It also means that when I search for this title as a keyword and then limit the Library location to Special Collections, this item no longer appears among the results.
In addition, within the record itself, its format is given as "Manuscript, Book" (and very prominently, I might add). But neither is accurate, and users who use the "Visual Material" facet also lose this item from their results list, even though that is the most logical format option for a single photograph.
The text was updated successfully, but these errors were encountered: