| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
If there’s a preferred citation note, then this note will display as the citation, followed by the URI and the current date. If there are multiple preferred citation notes, then these notes will be concatenated together. Please also note that the preferred citation note can be inherited, if desired, so that it is will always be used when the Citation action button is clicked by a user. In all cases, the preferred citation note that’s been added in the staff interface will *only* appear when a user clicks the Citation action button in the public interface. By default it , this particular note is not repeated anywhere else in the public interface.
...
In all cases, the current date that’s provided in the citation is preceded by the word “Accessed” by default“Accessed."
Example:
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.
WhereIn this example:
“Notebook, Bali and C[hinese] Theatre Notes, 1932” is the Display String, which is constructed as 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 objectArchival Object, which is a configurable inheritance option for the new public interface.
“Yale University Library Special Collections” is the repository Repository name.
“http://pui.hudmol.com/repositories/3/archival_objects/1280” is the URI of the archival object upon 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.
...
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.
...
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, selected in the Staff interface, 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 Public interface. There are no facets added to included in the Public interface to differentiate between these four possible display options.
...
For any collection that has top containers linked to it, there will be a new search-resutls page in the public Public interface that returns all of the top containers associated with that collection. On On this page, one of the two possible facets that can display here are Series titles. Please 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.
...
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:
Digital object links / thumbnails
...
Add some examples of how two can be used in tandem.
Please note , that the “make representative” feature that’s in the staff interface is not yet used in the Public Interfaceinterface. The following user story in JIRA might eventually be implemented so that a staff user can determine which digital object link to highlight: AR-XXXX.
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. Should actually move this to the other PUI documentation page.
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
...hopefully none to report, but will likely have a few
(e.g. when container type is missing, the text "Container " plus the container indicator are displayed in the badge on the landing page of an Accession record, but the text Container is missing from the badge on a search-result page).
...
...
Appendices
Appendix A
...