| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
Notebook, Bali and C[hinese] Theatre Notes, 1932. Harold Acton papers, GEN MSS 663. Series III. Yale University Library Special Collections. http://pui.hudmol.com/repositories/3/archival_objects/1280 Accessed July 09, 2017.
Where:
“Notebook, Bali and C[hinese] Theatre Notes, 1932” is the Display String, which is constructed as the title of the archival object, concatenated with a comma and the first (but only the first!) date subrecord, as per the rules in place in the ArchivesSpace staff interface.
“Harold Acton papers” is the Resource title.
“GEN MSS 663. Series III.” is the composite identifier for the archival object, which is a configurable inheritance option for the new public interface.
“Yale University Library Special Collections” is the repository name.
“http://pui.hudmol.com/repositories/3/archival_objects/1280” is the URI of the archival object upon which the user has clicked the Citation action button.
“July 09, 2017” is the date when the Citation action button was clicked.
Resource / Archival Object badges
Resource and archival object pages are created by the combination of two different elements from the staff interface, only one of which is a required element:
- Level of description
- Analog Instance preview information – a combination of container type(s) and container indicator(s)
For example, a file-level description that's linked to an analog instance of Box 1, Folder 1, would have a badge equal to "File - Box 1; Folder 1".
...
Multiple analog instances
xxx This badge displays on the landing page of the record as well as on search-result pages.
In there are multiple analog instances attached to that particular level of description, then the generic text "Multiple Containers" will display in place of any container information. In those cases, you will need to look in the Physical Storage Information accordion section to see more information about the multiple container groupings.
Digital Object badges
By default, the Digital Object display badge will show up as "Digital Record." If the VRA core option of Collection, Image, or Work is used, then that will change the badge display to "Digital Collection", "Digital Image", or "Digital Work", respectively. This will only affect display in the default public user interface. There are no facets added to the interface to differentiate between these four possible display options.
Series-based facets for top containers
xxxFor any collection that has top containers linked to it, there will be a new search-resutls page in the public interface that returns all of the top containers associated with that collection. On this page, one of the two possible facets that can display here are Series titles. Please note that the Series will only appear as a facet if it has an identifier in the staff interface. This limitation could be changed in a future release, but right now it is in place due to how the Top Container information is constructed on the staff-side of the application.
Internal linking
You can use the “ref” EAD element along with it’s @href attribute in the staff interface to provide internal links within the same finding aid in the public interface. The advantage of using this… Here’s an example:
...
Links between digital object records and accessions, resources, and archival objects
...just a place to note how the full hierarchy is displayed on the digital object pages, where the actual linkable occurs at the level that's bolded.
Agent links
Please note that if you provide a description of a relationship between two agents, the same description will appear on both agent landing pages. This behavior is the same in the staff interface as it is now in the public interface. You will need to keep this in mind when authoring any descriptive notes for agent relationships, since you cannot have two different descriptions written from different perspectives associated with the same relationship in ArchivesSpace 2.1. For example, if you were to link an agent record for Vincent Price and his mother, Marguerite Cobb Price, in the staff interface, it would be best to have the note reference both names since the same note will appear on both Vincent’s landing page as well as Marguerite’s, assuming that both agent records are published in the staff interface.
...
See this JIRA ticket for the mappings used in ArchivesSpace 2.1 (but note that the Repository mappings have not yet been put into place): https://archivesspace.atlassian.net/browse/AR-1484
You can test out these new features by going to Google’s Structured Data Testing Tool, https://search.google.com/structured-data/testing-tool, and pasting in a URI from the public interface for a resource or person/corporate body agent record.
...
Title (direct inheritance)
Identifier (indirect inheritance, but it is advised to inherit this element in a composite fashion once it is determined whether the level of description should or should not display as part of the identifier, which will depend upon local data-entry practices)
Language note, or code (direct inheritance, but there is a bug keeping this from displaying with the 2.1 release; when fixed, it should be set to indirect by default.)
Dates (direct inheritance)
Extents (direct inheritance... should be changed to indirect by default)
Creator (indirect inheritance)
Access restrictions note (direct inheritance)
Scope and contents note (indirect inheritance)
See https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L296-L396 for more information and examples.
Also, a video overview of this feature, which was recorded before development was finished, is available online: https://vimeo.com/195457286
Request action button
By default, this action button is turned off. This feature has been configured in the Test Corpus, however, so that a Gmail email account is used to 1) email users with information about their request, and 2) to email staff detailed information about the user’s request. The information that is included in a request is detailed in the following JIRA ticket: https://archivesspace.atlassian.net/browse/AR-1660
See https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L493-L524 for more information about how to configure this option.
...
Search the configuration file, https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb, for “pui” and “public” for other options that can be configured easily.
The labels used in the PUI may also be configured in whichever YML file is used: https://github.com/archivesspace/archivesspace/tree/master/public/config/locales
Known Bugs
...
...
...
Appendices
...