| 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.
In this example:
“Notebook, Bali and C[hinese] Theatre Notes, 1932” is the Display String, which is constructed from the title of the archival object, concatenated with a comma and the first (but only the first!) date subrecord, if there is a 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 for which the user has clicked the Citation action button.
“July 09, 2017” is the date when the Citation action button was clicked.
...
For any collection that has top containers linked to it, there will be a new search-resutls page results 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.
...
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 by default the identifier inherits from ancestor archival objects only; it does NOT include the resource identifier.
also 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 code (direct inheritance, but it does NOT display anywhere in the interface currently; eventually, this could be used for faceting)
Dates (direct inheritance)
Extents (indirect inheritance)
Creator (indirect inheritance)
Access restrictions note (direct inheritance)
Scope and contents note (indirect inheritance)
- Language of Materials note (indirect inheritance, but there seems to be a bug right now so that the Language notes always show up as being directly inherited. See AR-XXXX)
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
Composite Identifier Inheritance
...
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
(links to JIRA still need to be added for each bug)
...