Search Technologies Assessment
National Archives and Records AdministrationNational Archives Catalog (The Catalog)Archival Description Data Model Design– Catalog Perspective –Status-FinalVersion 1.15September 3, 2015National Archives & Records AdministrationNARA Catalog Archival Descriptions Data Model Design Lisong LiuPaul NelsonMadhu KoneniKristy MartinVersion 1.15Contract Number GS-35F-0541UOrder Number NAMA-13-F-0120September 3, 2015Contents TOC \o "2-3" \h \z \t "Heading 1,1" 1Overview PAGEREF _Toc425517321 \h 41.1Introduction to Archival Descriptions PAGEREF _Toc425517322 \h 41.2What is a DMD? PAGEREF _Toc425517323 \h 51.3Document Conventions PAGEREF _Toc425517324 \h 72DAS XML PAGEREF _Toc425517325 \h 83File Processing and Parsing PAGEREF _Toc425517326 \h 93.1Create the Catalog Information Package (OPA-IP) PAGEREF _Toc425517327 \h 93.2Download Files PAGEREF _Toc425517328 \h 103.3Extract Technical Metadata PAGEREF _Toc425517329 \h 103.3.1Images PAGEREF _Toc425517330 \h 103.3.2Video PAGEREF _Toc425517331 \h 123.3.3Audio Files PAGEREF _Toc425517332 \h 133.3.4Documents PAGEREF _Toc425517333 \h 143.4Create Catalog Renditions PAGEREF _Toc425517334 \h 213.4.1Text Content Rendition PAGEREF _Toc425517335 \h 213.4.2Image Thumbnails PAGEREF _Toc425517336 \h 213.4.3Image Tiles PAGEREF _Toc425517337 \h 213.5Create Objects File PAGEREF _Toc425517338 \h 224Mapping to Index Fields PAGEREF _Toc425517339 \h 244.1Mappings for Digital Objects and Archival Descriptions PAGEREF _Toc425517340 \h 244.2Mapping Table PAGEREF _Toc425517341 \h 244.3DateQualifer mapping PAGEREF _Toc425517342 \h 324.4Keyword search relevancy mapping PAGEREF _Toc425517343 \h 325Search Fields PAGEREF _Toc425517344 \h 385.1Advanced Search Fields PAGEREF _Toc425517345 \h 385.2Search Fields - Additional Information PAGEREF _Toc425517346 \h 395.2.1Date range field sources PAGEREF _Toc425517347 \h 395.2.2Recurring date search field sources PAGEREF _Toc425517348 \h 395.2.3Exact date search field sources PAGEREF _Toc425517349 \h 405.2.4Type of Archival Materials Values PAGEREF _Toc425517350 \h 405.2.5Level of Description Values PAGEREF _Toc425517351 \h 405.2.6File Format Values PAGEREF _Toc425517352 \h 405.2.7Location values PAGEREF _Toc425517353 \h 416Search Results Presentation PAGEREF _Toc425517354 \h 447Content Details Presentation PAGEREF _Toc425517355 \h 467.1Rules for ${online-availability-header} PAGEREF _Toc425517356 \h 467.2Rules for displaying fields PAGEREF _Toc425517357 \h 467.2.1Email addresses PAGEREF _Toc425517358 \h 467.3Record Group PAGEREF _Toc425517359 \h 467.3.1Record Group Link Table PAGEREF _Toc425517360 \h 487.4Collection PAGEREF _Toc425517361 \h 497.4.1Collection Link Table PAGEREF _Toc425517362 \h 507.5Series PAGEREF _Toc425517363 \h 517.5.1Series Link Table PAGEREF _Toc425517364 \h 567.6File Unit PAGEREF _Toc425517365 \h 577.6.1File Unit Link Table PAGEREF _Toc425517366 \h 627.6.1Electronic Records: Download Display Identifier PAGEREF _Toc425517367 \h 637.7Item PAGEREF _Toc425517368 \h 647.7.1Item Link Table PAGEREF _Toc425517369 \h 708Object Metadata Presentation PAGEREF _Toc425517370 \h 72Version ControlVersionDateReviewerSummary Description0.12013-10-25Paul Nelson and Madhu KoneniInitial Outline0.22013-11-22Paul Nelson & Rhea MandavilliAdditional Outline work0.32013-12-30Madhu Koneni & Rhea MandavilliUpdates to the sections 1, 1.1, 1.20.42014-02-24Lisong LiuTeam efforts to complete the document0.52014-02-25Paul Nelson & TeamReview sections 1-41.02014-02-25Paul Nelson & TeamReview sections 5-71.12014-03-19Lisong LiuUpdated based on NARA review and feedback in DCRF of 3/11/141.22014-03-31Lisong LiuTook out ARC XML format1.32014-04-22Lisong LiuIncorporate feedback from NARA/PPC1.42014-08-14Andrew GullettMake corrections:Add zip, tiff, and jpeg2000 to File Format Values table in 5.2.3.4.2 Mapping Table: I/creatorIds, I/donorIds, I/subjectIds, I/contributorIds, and I/personalReferenceIds use NAIDs instead of OPA-IDs.4.2 Mapping Table: I/dateRangeFacet additionally includes release, copyright, and broadcast dates.4.2 Mapping Table: Add scopeAndContentNote to I/content.4.2 Mapping Table: Change I/opaId prefix to “desc-“ to match API documents.4.2 Mapping Table: Change I/firstIngestDateTime to I/firstIngestedDateTime to match actual search index field name.4.4: Add parent creator names and location names to grank3.4.2 Mapping Table: Change I/oldScope to properly map ADs with and without digital objects.4.2 Mapping Table: Change I/iconType to properly map ADs with and without digital objects.4.2 Mapping Table: Change I/hmsEntryNumbers to only include HMS numbers.4.2 Mapping Table: Change to map itemAv to “item”.4.2 Mapping Table: Simplified I/hasOnline since browse requirements were removed from R1.1.52014-09-07Kristy MartinUpdated content:7.2 Record Group: To accommodate displaying Variant Control Number data for Record Groups as supported by the data.7.4 Series: Variant Control Numbers table to {VAR/variant-type/termName}.7.4 Series: Archived Copies, Copy N Media Information updated “Dimension” to reference the “termName”, also changed “technicalAccessNote” to “technicalAccessRequirementsNote”1.62014-11-14Kristy MartinRemoved “Confidential to Search Technologies” text from the footer.1.72014-11-24Carlos Araya/Brandon StahlMade corrections to 5.2.3 File Format Values to specify correct mime types for MP3, PowerPoint and Excel file types.Replaced url with url1.82014-12-11Kristy MartinUpdated locations, section 5.2.4 Location values (NARAOPA-395)1.92015-03-18Madhu Koneni, Kristy MartinFixed grank mappings in section 4.4; also in:7.27.3Updated the following sections to address Congressional fields for R1P2R1a:4.47.27.47.57.6Add content for later releases (HMS Entry Number, Finding Aid URL(:67.27.37.47.57.6Added Electronic Records section, 7.5.2; documents current implement of R1P1.1.102015-03-20Kristy MartinRemoved congressional fields from the grank table.Change beginCongress and endCongress fields to match the DAS specification1.112015-03-30Madhu KoneniComments from DRCF addressed. Section 4.4, 7.5.1.7.6 are updated1.122015-04-21Kristy Martin/Carlos Alberto ArrayaAdded Object Designator/Description section (8) and Advanced Search date fields for R1P2I1B in section 5.1. Fixed “filter” references in section 5.1.1.132015-07-09Kristy Martin, Alejandro BaltodanoChanged branding for system name throughout document. Added cover sheet.Added section 7.2Updated screenshots1.142015-07-24Kristy MartinUpdated content based on “DRCF_NAC R1P2 combined 1b_Increment 2 Design_IQS_Consolidated_7_21_15V1 (1).docx”1.152015-09-03Kristy MartinUpdated screenshots in section 6.OverviewThis is the Data Model Design document (DMD) for Archival Descriptions from the National Archives and Records Administration (NARA). This document aims to provide detailed data flow documentation for each and every archival description field as it is processed through the National Archives Catalog system, from reception from DAS, to presentation to the end user. The DMD is both a document and a process. It defines the following for each data source:How data is acquired from the original data source.A list of all source metadata elements.This includes files (digital objects) and renditionsHow metadata from the source is parsed and processedThis includes creating “Catalog renditions” such as thumbnails and tilesIt also includes text extraction and technical metadata extraction, as necessaryHow source data (metadata and files) is stored in Catalog storage (called opastorage; “opa” is a remnant from the previous name of the system)How source data is processed into Catalog search engine index fieldsWhat are the advanced search fieldsHow the search results (aka, the “brief results”) are formatted and filledHow content-detail pages (aka, the “full results”) are formatted and filledIntroduction to Archival DescriptionsArchival descriptions document the permanent holdings of the federal government in the custody of the National Archives and Records Administration (NARA). They include information on traditional paper holdings, electronic records, and artifacts.The archival descriptions data source to be indexed by the Catalog includes approximately 7-8 million archival description records which describe NARA holdings at various levels of granularity:The different level Archival Descriptions records are described at various levels of aggregation:Record Groups (~600) – Generally include records from one federal agency.Collections (~3000) – Are usually comprised of donated materials from a single person, family, or organizationSeries (~200,000) – Group materials originally filed together or because they resulted from a specific activity or are related in some other way.File Units (~5.4 million) – Group materials originally filed together in groups because they share specific characteristics, for example all correspondence with one individual, or a court case.Items (~1.3 million) – Are usually single documents, such as a letter, report, photograph, map, sound recordings or film.ItemAV – Are usually single documents Audio or Video filesThe definitions and metadata requirements for each type of description can be found in the Lifecycle Data Requirements Guide (LCDRG).The content of the archival descriptions are created and maintained by NARA subject matter experts. All the content is stored in the Description and Authority Services (DAS), formerly known as Archival Research Catalog (ARC).The information contained in archival descriptions is accessed using the National Archives Catalog system. Based on the user entered search parameters, the Catalog system retrieves descriptions and description metadata from the Search Engine Index.What is a DMD?The purpose of a Data Model Design document (DMD) is to document and describe all relevant data fields within a data source necessary to support all Catalog functionality. This metadata includes all data fields and their structure (nesting, type, number of values, etc.).The DMD further describes how metadata values are transformed and stored within the Catalog. This careful accounting of data processing is required to gain a complete understanding of how every bit and byte is handled through the Catalog system.Finally, the DMD also describes how metadata values are presented to the user, in the brief results, on the content detail page (aka the “full results”), from API calls, and in various metadata downloads.The following diagram shows all of the metadata mappings and their place in the Catalog system architecture:Specifically, this DMD includes the following:File Processing (section REF _Ref381085610 \r \h 3)Identifies how digital objects are gathered and stored in Catalog Storage (called opastorage; “opa” is a remnant from the previous name of the system)This includes metadata and digital object content extractionIndex Representation (section REF _Ref381085611 \r \h 4)How the Catalog content is represented in the search engine indexesThis includes business rules (concatenations, string processing, date formats, etc.) for transforming the ARC XML data so it can be stored in the Catalog indexes for efficient storageAdvanced Search Form Mappings (Section REF _Ref381085612 \r \h 5)Identifies each advanced search form filter and how it will be used for search.This includes mapping of advanced search form controls to index fields for search.Brief results presentation (section REF _Ref381085617 \r \h 6)Identifies how index fields are mapped to show the brief results.Content Detail (section REF _Ref381085624 \r \h 0)Identifies how fields from Catalog storage (“opastorage”) (DAS XML and digital objects) are mapped to the content detail page.Document ConventionsSince there are many different metadata fields for different purposes and from different systems, field mappings will be used throughout this document to clearly identify the originating source for every field, as follows:AbbrevDescriptionDASFields from the DAS <item>, <itemAv>, <fileUnit>, <series>, <collection> or <recordGroup>.For example, DAS/title will represent any of /series/title, /collection/title from DAS.IFields from the search engine index.For example, “I/title” will represent the title as it is stored in the search engine index for the record.OBJECTSobjects from the objects.xml table. See section REF _Ref381092364 \r \h 3.5 for more information.DAS XMLThe metadata used for constructing the Catalog archival descriptions will come directly from DAS, using DAS native XML format. The DAS XML format definition is available from NARA. The latest schema is “NaraDasUi1_1.xsd”.Using DAS XMLThere are several reasons for using native DAS XML format:This will always be the format directly supported by DAS production.Therefore, it will be the most up-to-date version of all fields available for descriptions from DAS.Content can be accessed per description / authority record.DAS will identify when a particular record is updated.When this record is updated, we can fetch it directly through DAS.When records are updated, all related content will need to be re-indexed.When a particular record is updated in DAS, the Catalog will need to identify and re-index all related content. This includes:Child archival descriptions (when a parent is changed)Child digital objects (when the container archival description is changed)Linked archival descriptions (when an authority record is changed)Child granules (when the container archival description is changed)When a child archival description is changed, the counts of the parent may need to be updated and the parent re-indexed. When an archival description is changed, the counts of the related authority records need to be updated and the parent re-indexed.Because of the complexity of re-processing and re-indexing content inside of the Catalog, getting only the original DAS XML is the best option.Further, the Catalog can decide what metadata changes will cause what sorts of reprocessing.This allows the Catalog to optimize exactly which records are re-indexed when a change is made.File Processing and ParsingFile processing for the Catalog requires a number of steps for processing digital objects, as shown in the following diagram:Each of these steps will be described in the following sections.Create the Catalog Information Package (OPA-IP)Every archival description with digital objects will be represented in Catalog storage (“opastorage”) as an “Information Package”, called an “OPA-IP” (“opa” is a remnant of the previous name of the system).And so, the first step for file processing will be to create a directory in Catalog storage (“opastorage”) with the following structure:/<NAID>/objects.xmlList of all content files with technical metadatadescription.xmlHolds a copy of the archival description XMLcontent/Digital-object-files go hereopa-renditions/Catalog-generated renditions go hereextracted-content/Extracted text and content metadata (doc properties)thumbnails/Thumbnails of digital objectsimage-tiles/Image tiles for low-bandwidth browsing of imagesNote: tags, comments, transcription and translations are saved in annotation database.Download FilesDigital object files will need to be cached in the Catalog for fast retrieval through the Catalog APIs. This is also required as part of the Catalog data management requirements.Initial Migration ProcessFor the initial bulk migration of OPA Pilot to Catalog Production, the following steps will be required:Go through all <digitalObjectArray> in the DAS XML.This would be all objects found in the DAS/digitalObjectArray/digitalObject.Download the digital file (based on the URL DAS/digitalObjectArray/digitalObject /accessFilename) from the media server.Store the digital file in the OPA-IP into the “content” directory.Incremental, “Day Forward” ProcessingThe process for copying new digital objects into the Catalog is specified in NARA Catalog Ingestion Design document.The anticipated process for copying new digital objects into the Catalog is expected to be:Periodically scan the “pre-ingestion” area for new digital objects.Copy those objects into the appropriate OPA-IP package, into the “content” directory.These objects would be specified in an ingestion package, such as a SIP (for simple objects) or an SEIP (for more complex objects).Objects should be copied from the “representation” directory from the SEIP into the “content” directory inside the OPA-IP.Extract Technical MetadataTechnical metadata extraction will be required for all digital objects. This will involve inspecting the contents of each metadata file to extract metadata inherent in the file type.Metadata extraction will be different for each different type of file.The file type of each file is based on calculated MIME.ImagesTechnical metadata will need to be extracted for the following image types:image/bmpimage/gifimage/jpegimage/jp2 [JPEG 2000 images are not in OPA pilot currently but NARA indicated that they want it to be supported]image/tiff [TIFF images are not in OPA pilot currently but NARA indicated that they want it to be supported]Technical Metadata Extraction ToolsThe tool which will be used to extract technical metadata from these formats is TIKA.Technical Metadata FieldsThe following technical metadata fields will be extracted for digital objects if the objects have the fields; not all objects will have all fields listed below:createDate – The date the image was created, as specified in the image metadata.metadataDate – The date the image metadata was created.modifyDate – The date the image was last modified, as specified in the image metadata.size – The size of the file in bytesmime – The IANA MIME type for the file formatdimensions – The X and Y dimensions for the image, with the following sub-elements:@x – The number of pixels of the image in the X dimension@y – The number of pixels of the image in the Y dimensionresolution – The X and Y resolution of the image, with the following sub-elements:@x – The X resolution of the image@y – The Y resolution of the image@units – The units for specifying the resolution, expected to be “pixels/inch” for all imagesbitsPerSample – The number of bits for each color dimension for each pixel in the image.Specified as three space-separated integers. Typically “8 8 8”photometricInterpretation – The color model for the image. Typically “RGB”.orientation – The image orientation. Can be any of:1 = horizontal (normal) 2 = mirrorHorizontal 3 = rotate180 4 = mirrorVertical 5 = mirrorHorizontalRotate270CW 6 = rotate90CW 7 = mirrorHorizontalRotate90CW 8 = rotate270CWsamplesPerPixel – The number of color components per pixel. Typically “3”.planarConfiguration – Indicates whether pixel components are recorded in “chunky” or “planar” format.colorSpace – The color space information tag (ColorSpace) is always recorded as the color space specifier. Normally sRGB (=1) is used to define the color space based on the PC monitor conditions and pression – The compression scheme used for the image data. When a primary image is JPEG compressed, this designation is not necessary and is omitted. When thumbnails use JPEG compression, this tag value is set to 6.software – The name and version of the software or firmware of the camera or image input device used to generate the image.Example<technicalMetadata> <createDate>2012-10-22T03:26:34Z</createDate> <metadataDate>2013-02-20T02:55:27Z</metadataDate> <modifyDate>2013-02-20T02:55:27Z</modifyDate> <size>1142680</size> <mime>image/jpeg</mime> <dimensions width="2181" height="2781"/> <resolution x="300" y="300" units="pixels/inch"/> <bitsPerSample>8 8 8</bitsPerSample> <photometricInterpretation>RGB</photometricInterpretation> <orientation>horizontal</orientation> <samplesPerPixel>3</samplesPerPixel> <planarConfiguration>chunky</planarConfiguration> <colorSpace>sRGB</colorSpace> <compression>uncompressed</compression> <software>Adobe Photoshop CS6 (Windows)</software></technicalMetadata>VideoTechnical metadata will need to be extracted for the following video types:video/mp4video/x-ms-wmv (WMV)video/aviapplication/vnd.rn-realmediaTechnical Metadata Extraction ToolsThe tool which will be used to extract technical metadata from these formats is TIKATechnical Metadata Fields and examplesThe following technical metadata fields will be extracted for digital objects if the objects have the fields; not all objects will have all fields listed below:Content-Length : 194506834Content-Type : video/mp4Creation-Date : 2013-06-25T19:38:00ZLast-Modified : 2013-06-25T19:38:06ZCreation-Date : 2013-06-25T19:38:00ZLast-Modified : 2013-06-25T19:38:06ZLast-Save-Date : 2013-06-25T19:38:06ZDate : 2013-06-25T19:38:06Zdcterms:created : 2013-06-25T19:38:00Zdcterms:modified : 2013-06-25T19:38:06Zmeta:creation-date : 2013-06-25T19:38:00Zmeta:save-date : 2013-06-25T19:38:06Zmodified : 2013-06-25T19:38:06ZresourceName : 208_143.mp4tiff:ImageLength : 0tiff:ImageWidth : 0xmpDM:audioChannelType : StereoxmpDM:audioSampleRate : 48000Audio FilesTechnical metadata will need to be extracted for the following audio types:audio/mpeg (MP3)Technical Metadata Extraction ToolsThe tool which will be used to extract technical metadata from these formats is TIKA.Technical Metadata Fields and examplesThe following technical metadata fields will be extracted for digital objects if the objects have the fields; not all objects will have all fields listed below:Author : nullContent-Length :58604223Content-Type : audio/mpegChannels : 2Creator : nulldc:creator : nulldc:title : 021-ILND-70C1384-Conlisk-01meta:author : nullresourceName : 021-ILND-70C1384-Conlisk-01.mp3samplerate : 44100title : 021-ILND-70C1384-Conlisk-01version : MPEG 3 Layer III Version 1xmpDM:album : nullxmpDM:artist : nullxmpDM:audioChannelType : StereoxmpDM:audioCompressor : MP3xmpDM:audioSampleRate : 44100xmpDM:duration :1833496.875xmpDM:genre : nullxmpDM:logComment : nullxmpDM:releaseDate : nullDocumentsTechnical metadata will need to be extracted for the following document types:application/pdftext/plainapplication/vnd.ms-powerpoint (PPT)application/mswordapplication/x-wri (Microsoft Write)application/vnd.ms-excel (Excel)text/html (Web Page)Technical Metadata Extraction ToolsThe tool (or tools) which will be used to extract technical metadata from these formats is TIKA.Technical Metadata Fields and ExamplesThe following technical metadata fields will be extracted for digital objects if the objects have the fields; not all objects will have all fields listed below:Application/pdfAllPermissions : 1048575Company : NARAContainer : DatabasesContent-Length : 136909Content-Type : application/pdfCreation-Date : 2012-07-25T16:07:19ZDateCreated : 4/21/2011 10:16:58 AMDisplayAllViewsOnSharePointSite : 1Last-Modified : 2012-07-25T16:10:08ZLast-Save-Date : 2012-07-25T16:10:08ZLastUpdated : 4/21/2011 10:16:58 AMName : UserDefinedOwner : adminPermissions : 1048575ReplicateProject : YesUserName : adminCreated : Wed Jul 25 12:07:19 EDT 2012Date : 2012-07-25T16:10:08Zdc:title : Federal Assistance Award Data System, Technical Specifications Summarydcterms:created : 2012-07-25T16:07:19Zdcterms:modified : 2012-07-25T16:10:08Zmeta:creation-date : 2012-07-25T16:07:19Zmeta:save-date : 2012-07-25T16:10:08Zmodified : 2012-07-25T16:10:08Zproducer : Acrobat Distiller 9.0.0 (Windows)resourceName : FAADS_TSS135.pdftitle : Federal Assistance Award Data System, Technical Specifications Summaryxmp:CreatorTool : Acrobat PDFMaker 9.0 for AccessxmpTPg:NPages : 22Text/plainContent-Encoding : ISO-8859-1Content-Length : 2820573 Content-Type : text/plain; charset\u003dISO-8859-1resourceName : cbp07prc.txtText/htmlPICS-Label : PICS-1.1 "" l r (s 0))Content-Language : en-USy_key : 0e94d8e9e5732ec6engine.cache : falseimagetoolbar : nodate : 2013-10-21distribution : globalContent-Encoding : windows-1252Content-Location : : generalresourceName : : National Archives and Records AdministrationApplication/vnd.ms-powerpoint? (PPT)Application-Name : Microsoft PowerPointAuthor : Ray HollandCompany : DOTContent-Length :18959360Content-Type : application/vnd.ms-powerpointCreation-Date : 2001-09-17T15:00:47ZEdit-Time :167793170000Last-Author : Preferred CustomerLast-Modified : 2001-09-19T14:56:41ZLast-Save-Date : 2001-09-19T14:56:41ZRevision-Number :39Slide-Count :247Word-Count :9733cp:revision :39creator : Ray Hollanddate : 2001-09-19T14:56:41Zdc:creator : Ray Hollanddc:title : PowerPoint Presentationdcterms:created : 2001-09-17T15:00:47Zdcterms:modified : 2001-09-19T14:56:41Zextended-properties:Application : Microsoft PowerPointextended-properties:Company : DOTmeta:author : Ray Hollandmeta:creation-date : 2001-09-17T15:00:47Zmeta:last-author : Preferred Customermeta:save-date : 2001-09-19T14:56:41Zmeta:slide-count :247meta:word-count :9733modified : 2001-09-19T14:56:41ZresourceName : 5 AWA 213 ATCSCC September 11.ppstitle : PowerPoint PresentationxmpTPg:NPages :247 Application/mswordApplication-Name : Microsoft Word 8.0Author : Dennis RoweCharacter Count :24377Comments :nullCompany : The MITRE CorporationContent-Length :95232Content-Type : application/mswordCreation-Date : 2002-04-19T18:49:00ZEdit-Time :53400000000Keywords :nullLast-Author : asignoreLast-Modified : 2002-04-24T16:59:00ZLast-Save-Date : 2002-04-24T16:59:00ZPage-Count :1Revision-Number :32Template : NormalWord-Count :4276comment :nullcp:revision :32cp:subject :nullcreator : Dennis Rowedate : 2002-04-24T16:59:00Zdc:creator : Dennis Rowedc:subject :nulldc:title : Appendix Mdcterms:created : 2002-04-19T18:49:00Zdcterms:modified : 2002-04-24T16:59:00Zextended-properties:Application : Microsoft Word 8.0extended-properties:Company : The MITRE Corporationextended-properties:Template : Normalmeta:author : Dennis Rowemeta:character-count :24377meta:creation-date : 2002-04-19T18:49:00Zmeta:keyword :nullmeta:last-author : asignoremeta:page-count :1meta:save-date : 2002-04-24T16:59:00Zmeta:word-count :4276modified : 2002-04-24T16:59:00ZresourceName : 5 AWA 199 Appendix M.docsubject : nulltitle : Appendix Mw:comments : nullxmpTPg:NPages : 1Application/vnd.ms-excel (Excel)Application-Name : Microsoft ExcelApplication-Version :12.0000,Author : M1CHJ00Content-Length :108858,Content-Type : application/vnd.openxmlformats-officedocument.spreadsheetml.sheetCreation-Date : 2002-11-20T19:42:53ZLast-Author : ImageLast-Modified : 2012-08-15T20:19:08ZLast-Printed : 2004-01-30T21:26:08ZLast-Save-Date : 2012-08-15T20:19:08Zcreator : M1CHJ00date : 2012-08-15T20:19:08Zdc:creator : M1CHJ00dc:publisher : FRBdcterms:created : 2002-11-20T19:42:53Zdcterms:modified : 2012-08-15T20:19:08Zextended-properties:AppVersion :12.0000,extended-properties:Application : Microsoft Excelextended-properties:Company : FRBmeta:author : M1CHJ00meta:creation-date : 2002-11-20T19:42:53Zmeta:last-author : Imagemeta:print-date : 2004-01-30T21:26:08Zmeta:save-date : 2012-08-15T20:19:08Zmodified : 2012-08-15T20:19:08Zprotected : falsepublisher : FRBresourceName : HMDA_CRA_2006_layout.xlsxApplication/x-wri? (Microsoft Write)no Microsoft Write samples in OPA PilotCreate Catalog RenditionsThe next step in file processing is to create file renditions required by the Catalog for the the Catalog user interface and other Catalog functions.Text Content RenditionText content will need to be extracted from all document files (MS-Word, PDF, Excel, etc.). The expected tool for text content processing (currently being reviewed as part of the Analysis of Alternatives) will be Apache Tika (see for more details).Since text extraction is a relatively slow process, extracted text content will be stored in the OPA-IP under “opa-renditions/extracted-content”, so that digital objects can be quickly and efficiently re-indexed as archival description records or annotations change.Extracted text content will be stored in XHTML format as produced by Apache Tika.Additional Business Rules:Text extraction will not be performed on any digital object where DAS/digitalObjectArray/digitalObject/in-database is set to “N”.Text extraction will occur if this field is missing OR if it contains “Y”.Image ThumbnailsThumbnails for all images, if not available for download from the media server, will need to be created.Images will be scaled down so that the maximum dimension (either X or Y) will be 200 pixels. The other dimension will be scaled appropriately to maintain the same aspect ratio as the original.Thumbnail images will be stored in the “opa-renditions/thumbnails” directory.The tool for creating thumbnails is VIPS.Image TilesVery large images, greater than 500K, will be converted into “tiles” so they can be efficiently downloaded and browsed by users with limited bandwidth (e.g. users on cell phones or tablets).Tiles will be stored in “DZI” format (Deep Zoom) – the format used by the Open Seadragon tool and a number of other image browers.Tiles for images will be stored in the “opa-renditions/tiles” directory.The tool for creating tiles is VIPS.Note that simpler image pyramids may be used for smaller files. For example, simple ? resolution and ? resolution files may be created, since these are easier and faster to create than image tiles. Open Seadragon can support both image formats.Create Objects FileThe final step in file processing is to create the objects.xml file. This file maintains the technical metadata for all files and ties all of the files together, so that all of the various renditions for each file are tied together.The current objects XML file format is described in section 2.3.1.2 of the NARA Catalog Public API Reference Guide. A sample of the file is shown below.<objects version="OPA-OBJECTS-1.0"> <object id="1" hasAnnotations="true"> <designator>1</designator> <file type="primary" path="./content/hst-ppp_93-1_18-01.jpg" mime="image/jpeg"> <technicalMetadata> <createDate>2012-10-22T03:26:34Z</createDate> <metadataDate>2013-02-20T02:55:27Z</metadataDate> <modifyDate>2013-02-20T02:55:27Z</modifyDate> <size>1142680</size> <mime>image/jpeg</mime> <dimensions width="2181" height="2781"/> <resolution x="300" y="300" units="pixels/inch"/> <bitsPerSample>8 8 8</bitsPerSample> <photometricInterpretation>RGB</photometricInterpretation> <orientation>horizontal</orientation> <samplesPerPixel>3</samplesPerPixel> <planarConfiguration>chunky</planarConfiguration> <colorSpace>sRGB</colorSpace> <compression>uncompressed</compression> <software>Adobe Photoshop CS6 (Windows)</software> </technicalMetadata> </file> <thumbnail path="./opa-rendition/thumbnails/hst-ppp_93-1_18-01-thumb.jpg" mime="image/jpeg"/> <imageTiles path="./opa-rendition/image-tiles/hst-ppp_93-1_18-01_jpg"/> </object> <object id="2"> <designator>2</designator> <file type="primary" path="./content/hst-ppp_93-1_18-02.jpg" mime="image/jpeg"> <technicalMetadata> . . Technical metadata for the primary file for the second object will go here . </technicalMetadata> </file> <thumbnail path="./opa-rendition/thumbnails/hst-ppp_93-1_18-02-thumb.jpg" mime="image/jpeg"/> <imageTiles path="./opa-rendition/image-tiles/hst-ppp_93-1_18-02_jpg"/> </object> <object id="3"> <designator>3</designator> <file type="primary" path="./content/hst-ppp_93-1_18-03.jpg" mime="image/jpeg"> <technicalMetadata> . . Technical metadata for the primary file for the third object will go here . </technicalMetadata> </file> <thumbnail path="./opa-rendition/thumbnails/hst-ppp_93-1_18-03-thumb.jpg" mime="image/jpeg"/> <imageTiles path="./opa-rendition/image-tiles/hst-ppp_93-1_18-03_jpg" type="DZI"/> </object></objects>Mapping to Index FieldsThe following table shows the mapping from the <DAS> fields (identified with prefix “DAS/” to the Catalog index fields (identified with prefix “I/”). See section REF _Ref381091079 \r \h 1.3 for all prefixes used in this document.See the NARA Catalog Public API Reference Guide and the NARA Catalog Search Engine Design documents for more information on each Catalog index field.Mappings for Digital Objects and Archival DescriptionsThere will be separate entries indexed into the Catalog for each digital object as well as the Archival Description as a whole. For example, if an archival description has 10 digital objects, there will be 11 entries in the Catalog index.For digital objects, all fields mapped to “DAS/” will refer to the fields in archival description to which the digital object belongs, except, for fields mapped from DAS/digitalObjectArray/digitalObject. In this case, the fields will come from the digital object’s specific value.Similarly for the OBJECTS/ fields (from the objects table). For descriptions, the entire OBJECTS/ objects table will be mapped into the associated index field. But for digital objects, only the portion of the OBJECTS table appropriate for the specified digital object (indexed by object ID) will be mapped into the Catalog index field for the digital object.Mapping TableIndex FieldXML document elementPurposeI/naIdDAS/naIdresults, sorting, searchI/opaId“desc-”+ {DAS/naId}Example: desc-5132492results, sorting, searchI/containerIdOne of the following:DAS/physicalOccurrenceArray/itemPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/containerIdDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/containerIdDAS/physicalOccurrenceArray/fileUnitPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/containerIdDAS/physicalOccurrenceArray/seriesPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/containerIdresults, searchI/localIdDAS/localIdentifierresults, sorting, searchI/url“”+{DAS/naId}results, searchI/accessPathFor Descriptions: “id/”+{DAS/naId}Example: id/7229423For Objects: “id”+{DAS/naId} + ”/” + {OBJECTS/object/@id}resultI/dateRangeFacetBucket as in API doc 3.4.4:centuries to 1699 (1600 - 1699)half-centuries in 1700s (1700 - 1749, 1750 - 1799)decades from 1800 (1820 - 1829)DAS/inclusiveDates/inclusiveStartDateDAS/inclusiveDates/inclusiveEndDateDAS/coverageDates/coverageStartDateDAS/coverageDates/coverageEndDateDAS/productionDateArray/proposableQualifiableDate/yearDAS/releaseDateArray/proposableQualifiableDate/yearDAS/copyrightDateArray/proposableQualifiableDate/yearDAS/broadcastDateArray/proposableQualifiableDate/yearDAS/parent*/inclusiveDates/inclusiveStartDate/yearDAS/parent*/inclusiveDates/inclusiveEndDate/yearresults, facet, searchI/type“description” for archival description or “object” for digital objectresults, facet, searchI/oldScope“descriptions” for archival description without digital objects.“online” for archival description with digital objects.“online” for digital object.results, facet, searchI/levelroot tag of DAS record. Enumeration of value is:“recordGroup”“collection”“series”“fileUnit”“item” for both item and itemAv“object” (for all digital objects)results, facet, searchI/parentLevelDAS/parent[Level]Based on the value of Level:“RecordGroup” “recordGroup”“Collection” “collection”“Series” “series”“FileUnit” “fileUnit”results, searchI/iconTypeFor descriptions without digital objects:Based on the value of I/level“recordGroup” “nara/record-group”“collection” “nara/collection”“series” “nara/series”“fileUnit” “nara/file-unit”“item” “nara/item”“itemAv” “nara/item”For descriptions with digital objects:OBJECTS/object[1]/file[@type=’primary’]/@mimeFor all digital objects:OBJECTS/object/file[@type='primary']/@mime (normalized)results, searchI/fileFormatFor descriptions:The list of all unique, normalized mime types from:OBJECTS/object/file[@type='primary']/@mime (normalized)For digital objects:OBJECTS/object/file[@type='primary']/@mime (normalized)results, facet, searchI/originalMimeTypeOBJECTS/object/file[@type='primary']/@mimeNote: Not normalizedsearchI/tabType“all” will be added to all entries for this field.For descriptions:Add multiple entries to this field for each:OBJECTS/object/file[@type='primary']/@mime (normalized)Map each mime type to the “type” field from the table in section REF _Ref380594510 \r \h 5.2.6.Add “online” of DAS/digitalObjectArray exists OR OBJECTS/object exists.For digital objects:Add a single additional entry for:OBJECTS/object/file[@type='primary']/@mime (normalized)Map the mime type to the “type” field from the table in section 5.2.6.Add “online” for all digital objects.result, searchI/materialsTypeDAS/generalRecordsTypeArray/generalRecordsType/termNameresults, facet, searchI/title{DAS/title} + “ - “ + {DAS/subtitle}NOTE: Do not include the “ - “ if there is no DAS/subtitleresults, searchI/titleSortDAS/title with leading articles and prepositions removedArticles include: “the”, “an”, “a”Prepositions include: “of”, “by”, “in”, “on”, “as”, “at”, “for”, “to”sorting, searchI/allTitlesThis will be a multi-valued field which contains:DAS/titleDAS/subtitleDAS/otherTitleArray/otherTitle/titleDAS/productionSeriesTitleDAS/productionSeriesSubtitleIf there are multiple of any of these titles, all should be added into I/allTitlesresults, searchI/hmsEntryNumbersDAS/variantControlNumberArray/variantControlNumber/number where DAS/variantControlNumberArray/variantControlNumber/type/termName indicates type: “HMS/MLR Entry Number”results, searchI/hmsEntryNumberSortSteps:Sort all {I/hmsEntryNumbers} alphabetically.Concatenate into a single string.results, sortingI/parentTitleDAS/parent[Level]/titleenumeration of Level:RecordGroupCollectionSeries FileUnitresults, searchI/contentDAS/scopeAndContentNote.Extracted data from digital object. See section REF _Ref381094720 \r \h 3.4.1.results, searchI/creatorsDAS/creatingIndividualArray/creatingIndividual/creator/termNameORDAS/creatingOrganizationArray/creatingOrganization/creator/termNamesearchI/teasersubstring(I/content, 500)results, searchI/isOnline“true” for all digital objects and archival description which contains a digital objectresults, searchI/hasOnline“true” for all digital objects.“true” for descriptions with digital objects.results, searchI/thumbnailFileFor descriptions:OBJECTS/object[1]/thumbnail/@pathFor digital objects:OBJECTS/object/thumvnail/@pathresultI/titleDateconcat(DAS/inclusiveDates/inclusiveStartDate, “ - ” DAS/inclusiveDates/inclusiveEndDate)results, searchI/locationAdd an entry for every:DAS/physicalOccurrenceArray/itemPhysicalOccurrence/ referenceUnitArray/referenceUnit/termNameDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ referenceUnitArray/referenceUnit/termNameDAS/physicalOccurrenceArray/fileUnitPhysicalOccurrence/ referenceUnitArray/referenceUnit/termNameDAS/physicalOccurrenceArray/seriesPhysicalOccurrence/ referenceUnitArray/referenceUnit/termNameNote:recordGroup and collection shall have location too, but DAS schema does not show that. In case the physicalOccurenceArray is added, it will be populated as:DAS/physicalOccurrenceArray/collectionPhysicalOccurrence/referenceUnitArray/referenceUnit/termNameDAS/physicalOccurrenceArray/recordGroupPhysicalOccurrence/referenceUnitArray/referenceUnit/termNameresults, searchI/locationKeywordsAdd an entry for every tokenized:DAS/physicalOccurrenceArray/itemPhysicalOccurrence/ referenceUnitArray/referenceUnit/termNameDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ referenceUnitArray/referenceUnit/termNameDAS/physicalOccurrenceArray/fileUnitPhysicalOccurrence/ referenceUnitArray/referenceUnit/termNameDAS/physicalOccurrenceArray/seriesPhysicalOccurrence/ referenceUnitArray/referenceUnit/termNameNote:recordGroup and collection shall have location too, but DAS schema does not show that. In case the physicalOccurenceArray is added, it will be populated as:DAS/physicalOccurrenceArray/collectionPhysicalOccurrence/referenceUnitArray/referenceUnit/termNameDAS/physicalOccurrenceArray/recordGroupPhysicalOccurrence/referenceUnitArray/referenceUnit/termNamesearchI/locationIdsAdd an entry for every:DAS/physicalOccurrenceArray/itemPhysicalOccurrence/ referenceUnitArray/referenceUnit/naIdDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ referenceUnitArray/referenceUnit/naIdDAS/physicalOccurrenceArray/fileUnitPhysicalOccurrence/ referenceUnitArray/referenceUnit/naIdDAS/physicalOccurrenceArray/seriesPhysicalOccurrence/ referenceUnitArray/referenceUnit/naIdNote:recordGroup and collection shall have location ID too, but DAS schema does not show that. In case the physicalOccurenceArray is added, it will be populated as:DAS/physicalOccurrenceArray/collectionPhysicalOccurrence/referenceUnitArray/referenceUnit/naIdDAS/physicalOccurrenceArray/recordGroupPhysicalOccurrence/referenceUnitArray/referenceUnit/naIdresults, facet, searchI/parentNaIdDAS/parent*/naIdresults, searchI/ancestorNaIdsAdd an entry for every:DAS/parent[Level]/naIdDAS/parent[Level]/parent[Level]/naIdDAS/parent[Level]/parent[Level]/parent[Level]/naIdenumeration of Level:RecordGroupCollectionSeries FileUnitresults, searchI/hasChildren“true” if this record has children in the archival hierarchyresults, searchI/objectIdOBJECTS/object/@idaccess, searchI/objectSortNumIf the record contains both images and documents, re-sort all of the OBJECTS/object with images first (sub-sort by the position in which the object occurs in the DAS XML) and then documents last (sub-sort by the position in which the object occurs in the DAS XML).Then set I/objectSortNum to the new sorted order.search, sortingI/fileSizeOBJECTS/object/file[@type='primary']/technicalMetadata/sizesearchI/objectDesignatorOBJECTS/object/designatorresultsI/objectDescriptionOBJECTS/object/descriptionsearchI/descriptionIf record is archival description:XML content of archival descriptioncontent deliveryI/technicalOBJECTS/object/technicalMetadatasearchI/objectsFor descriptions:OBJECTS = entire objects.xml from section REF _Ref381095656 \r \h 3.5.(NOTE: Copy the Transcription, Translation and seData XML into the objects XML before indexing)For digital objects:OBJECTS/object = Just the objects.xml for the specified object(NOTE: Copy the Transcription, Translation and seData XML into the objects XML before indexing)I/allAuthorityIdsAdd an entry for every:I/creatorIds, I/donorIds, I/subjectIds, I/contributorIds, I/personalReferenceIdssearchI/creatorIdsAdd an entry for every: DAS/creatingIndividualArray/creatingIndividual/creator/naIdORDAS/creatingOrganizationArray/creatingOrganization/creator/naIdsearchI/donorIdsAdd an entry for every: DAS/organizationalDonorArray/organizationName/naId ORDAS/personalDonorArray/person/naId ORDAS/archivalDescriptionsDonorArray/descriptionReference/naIdsearchI/subjectIdsAdd an entry for every: DAS/personalReferenceArray/person/naIdDAS/organizationalReferenceArray/organization/naIdDAS/geographicReferenceArray/geographicPlaceName/naIdDAS/descriptionReferenceArray/ descriptionReference/naIdsearchI/contributorIdsAdd an entry for every: DAS/organizationalContributorArray/organizationName/naIdDAS/personalContributorArray/person/naIdDAS/archivalDescriptionsContributorArray/descriptionReference/naIdsearchI/personalReferenceIdsAdd an entry for every: DAS/personalReferenceArray/person/naIdsearchI/recordCreatedDateTimeDAS/recordHistory/created/dateTimeresults, sortingI/recordUpdatedDateTimeDAS/recordHistory/changed/modification/dateTimeresults, sortingI/firstIngestedDateTimeThe date/time the index-entry was first ingested into the Catalog.Note: This will need to be maintained by the Catalog in a caching table.results, sortingI/ingestedDateTimenow() = The current date-time.results, sortingI/productionDateDAS/productionDateArray/proposableQualifiableDateresults, sortingI/productionDateMonthDAS/productionDateArray/proposableQualifiableDatesearchI/productionDateDayDAS/productionDateArray/proposableQualifiableDatesearchI/productionDateYearDAS/productionDateArray/proposableQualifiableDatesearchI/productionDateQualifiersee section 4.3resultI/broadcastDateDAS/broadcastDateArray/proposableQualifiableDateresults, sortingI/broadcastDateMonthDAS/broadcastDateArray/proposableQualifiableDatesearchI/broadcastDateDayDAS/broadcastDateArray/proposableQualifiableDatesearchI/broadcastDateYearDAS/broadcastDateArray/proposableQualifiableDatesearchI/broadcastDateQualifiersee section 4.3resultI/releaseDateDAS/releaseDateArray/proposableQualifiableDateresults, sortingI/releaseDateQualifiersee section 4.2resultI/coverageStartDateDAS/coverageDates/coverageStartDateresults, sortingI/coverageStartDateMonthDAS/coverageDates/coverageStartDatesearchI/coverageStartDateDayDAS/coverageDates/coverageStartDatesearchI/coverageStartDateYearDAS/coverageDates/coverageStartDatesearchI/coverageStartDateQualifiersee section 4.2resultI/coverageEndDateDAS/coverageDates/coverageEndDateresults, sortingI/coverageEndDateMonthDAS/coverageDates/coverageEndDatesearchI/coverageEndDateDayDAS/coverageDates/coverageEndDatesearchI/coverageEndDateYearDAS/coverageDates/coverageEndDatesearchI/coverageEndDateQualifiersee section 4.2resultI/inclusiveStartDateDAS/inclusiveDates/inclusiveStartDateresults, sortingI/inclusiveStartDateMonthDAS/inclusiveDates/inclusiveStartDatesearchI/inclusiveStartDateDayDAS/inclusiveDates/inclusiveStartDatesearchI/inclusiveStartDateYearDAS/inclusiveDates/inclusiveStartDatesearchI/inclusiveStartDateQualifiersee section 4.2resultI/inclusiveEndDateDAS/inclusiveDates/inclusiveEndDateresults, sortingI/inclusiveEndDateMonthDAS/inclusiveDates/inclusiveEndDatesearchI/inclusiveEndDateDayDAS/inclusiveDates/inclusiveEndDatesearchI/inclusiveEndDateYearDAS/inclusiveDates/inclusiveEndDatesearchI/inclusiveEndDateQualifiersee section 4.2resultDateQualifer mappingFor most of the date fields inside archival description record, they also have relevant DateQualifier fields which are used to describe accuracy of the date fields. These date fields includes: productionDate, broadcastDate, releaseDate, coverageStartDate, coverageEndDate, inclusiveStartDate, inclusiveEndDate. The value of each of the DateQualifier fields will be based on the date format of the corresponding date as it is represented in the DAS XML. The mapping will be as follows:Y – If the date contains only a year and no additional characters, date is knownY? – If the date contains only a year and the “?” character, for example: “1944?”, date is uncertainYca – If the date contains only a year and the “ca.” string, for example: “ca. 1944”, date is approximateYM – If the date contains only year and month, no additional characters, date is knownYM? – If the date contains only year, month and the “?” character, for example: “01/1944?”, date is uncertainYMca – If the date contains only year, month and “ca.” string, for example: “ca. 01/1944”, date is approximateYMD – If the date contains Full date: year, month and day, date is knownKeyword search relevancy mappingArchival Description metadata will be mapped to the Catalog relevancy model as follows. Note that all of the fields specified (grank1, grank2, grank3, grank4, and content) will be searched by all “q=” parameters.When multiple DAS/ fields are mapped to the same relevancy field, all of their content will be concatenated together into the same field and searched together.Source fieldRelevancy FieldDAS/naIdI/grank1DAS/recordGroupNumberI/grank2DAS/collectionIdentifierI/grank2DAS/titleI/grank2DAS/otherTitleArray/otherTitle/titleI/grank2DAS/subtitleI/grank2DAS/localIdentifierI/grank2DAS/recordsCenterTransferArray/recordsCenterTransferNumber/numberI/grank2DAS/accessionNumberArray/accessionNumber/numberI/grank2DAS/variantControlNumberArray/variantControlNumber/numberI/grank2DAS/microformPublicationArray/microformPublication/microformPublicationTitle/identifierI/grank2DAS/productionSeriesTitleI/grank2DAS/productionSeriesSubtitleI/grank2DAS/organizationalDonorArray/organizationName/termName ORDAS/personalDonorArray/person/termName ORDAS/archivalDescriptionsDonorArray/descriptionReference/titlei/grank3DAS/organizationalContributorArray/organizationalContributor/contributor/termName ORDAS/personalContributorArray/personalContributor/contributor/termName ORDAS/archivalDescriptionsContributorArray/descriptionReference/titlei/grank3DAS/creatingIndividualArray/creatingIndividual/creator/termNameORDAS/creatingOrganizationArray/creatingOrganization/creator/termNamei/grank3DAS/personalReferenceArray/person/termNameDAS/organizationalReferenceArray/organization/termNameDAS/geographicReferenceArray/geographicPlaceName/termNameDAS/descriptionReferenceArray/descriptionReference/titlei/grank3DAS/scopeAndContentNotei/grank3DAS/*[starts-with(local-name(), 'parent')]/creatingIndividualArray/creatingIndividual/creator/termNameDAS/*[starts-with(local-name(), 'parent')]/creatingOrganizationArray/creatingOrganization/creator/termNamei/grank3DAS/physicalOccurrenceArray/*/referenceUnitArray/referenceUnit/termNamei/grank3DAS/dateNotei/grank4DAS/custodialHistoryNotei/grank4DAS/scaleNotei/grank4DAS/transferNotei/grank4DAS/arrangementi/grank4DAS/accessRestriction/accessRestrictionNotei/grank4DAS/accessRestriction/status/termNamei/grank4DAS/useRestriction/ status/termNamei/grank4DAS/onlineResourceArray/onlineResource/urli/grank4DAS/shotListi/grank4DAS/physicalOccurrenceArray/fileUnitPhysicalOccurrence/ physicalOccurrenceNoteDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ physicalOccurrenceNoteDAS/physicalOccurrenceArray/itemPhysicalOccurrence/ physicalOccurrenceNoteDAS/physicalOccurrenceArray/seriesPhysicalOccurrence/ physicalOccurrenceNotei/grank4DAS/physicalOccurrenceArray/SeriesPhysicalOccurrence/containerListi/grank4DAS/dispositionAuthorityNumberArray/dispositionAuthorityNumber/numberi/grank4DAS/variantControlNumberArray/variantControlNumber/type/termNamei/grank4DAS/variantControlNumberArray/variantControlNumber/notei/grank4DAS/digitalObjectArray/digitalObject/objectDescriptioni/grank4DAS/generalNoteArray/generalNote/notei/grank4DAS/microformPublicationArray/microformPublication/notei/grank4DAS/microformPublicationArray/microformPublication/publication/titlei/grank4DAS/physicalOccurrenceArray/itemPhysicalOccurrence/ mediaOccurrenceArray/itemmediaOccurrence/technicalAccessRequirementsNoteDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ mediaOccurrenceArray/itemAvmediaOccurrence/technicalAccessRequirementsNoteDAS/physicalOccurrenceArray/fileUnitPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/technicalAccessRequirementsNoteDAS/physicalOccurrenceArray/seriesPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/technicalAccessRequirementsNotei/grank4DAS/formerRecordGroupArray/recordGroup/recordGroupNumber ? or titleDAS/formerCollectionArray/collection/collectionIdentifier ? or titleDAS/parentSeries/formerRecordGroupArray/recordGroup/recordGroupNumber ? or titleDAS/parentSeries/formerCollectionArray/collection/collectionIdentifier ? or titleDAS/parentFileUnit/formerRecordGroupArray/recordGroup/recordGroupNumber ? or titleDAS/parentFileUnit/formerCollectionArray/collection/collectionIdentifier ? or titlei/grank4DAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ mediaOccurrenceArray/itemAvmediaOccurrence/recordingSpeed/termNamei/grank4DAS/physicalOccurrenceArray/itemPhysicalOccurrence/ mediaOccurrenceArray/itemmediaOccurrence/color/termNameDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ mediaOccurrenceArray/itemAvmediaOccurrence/color/termNameDAS/physicalOccurrenceArray/fileUnitPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/color/termNameDAS/physicalOccurrenceArray/seriesPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/color/termNamei/grank4DAS/physicalOccurrenceArray/itemPhysicalOccurrence/ mediaOccurrenceArray/itemmediaOccurrence/dimension/termNameDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ mediaOccurrenceArray/itemAvmediaOccurrence/dimension/termNameDAS/physicalOccurrenceArray/fileUnitPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/dimension/termNameDAS/physicalOccurrenceArray/seriesPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/dimension/termNamei/grank4DAS/physicalOccurrenceArray/itemPhysicalOccurrence/ mediaOccurrenceArray/itemmediaOccurrence/base/termNameDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ mediaOccurrenceArray/itemAvmediaOccurrence/base/termNamei/grank4DAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ mediaOccurrenceArray/itemAvmediaOccurrence/soundtrackLanguage/termNamei/grank4DAS/physicalOccurrenceArray/itemPhysicalOccurrence/ mediaOccurrenceArray/itemmediaOccurrence/specificMediaType/termNameDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ mediaOccurrenceArray/itemAvmediaOccurrence/specificMediaType/termNameDAS/physicalOccurrenceArray/fileUnitPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/specificMediaType/termNameDAS/physicalOccurrenceArray/seriesPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/specificMediaType/termNamei/grank4DAS/physicalOccurrenceArray/itemPhysicalOccurrence/ mediaOccurrenceArray/itemmediaOccurrence/process/termNameDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ mediaOccurrenceArray/itemAvmediaOccurrence/process/termNameDAS/physicalOccurrenceArray/fileUnitPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/process/termNameDAS/physicalOccurrenceArray/seriesPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/process/termNamei/grank4DAS/physicalOccurrenceArray/itemPhysicalOccurrence/ mediaOccurrenceArray/itemmediaOccurrence/format/termNameDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ mediaOccurrenceArray/itemAvmediaOccurrence/format/termNamei/grank4DAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/soundtrackConfiguration/termNamei/grank4DAS/findingAidArray/findingAid/typei/grank4DAS/findingAidArray/findingAid/sourcei/grank4DAS/findingAidArray/findingAid/notei/grank4DAS/organizationalContributorArray/organizationalContributor/contributorType ORDAS/personalContributorArray/personalContributor/contributorType ORDAS/archivalDescriptionsContributorArray/descriptionReference/recordTypei/grank4DAS/generalRecordsTypeArray/generalRecordsType/termNamei/grank4DAS/physicalOccurrenceArray/itemPhysicalOccurrence/copyStatus/termNameDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/copyStatus/termNameDAS/physicalOccurrenceArray/fileUnitPhysicalOccurrence/ copyStatus/termNameDAS/physicalOccurrenceArray/seriesPhysicalOccurrence/ copyStatus/termNamei/grank4DAS/physicalOccurrenceArray/itemPhysicalOccurrence/ mediaOccurrenceArray/itemmediaOccurrence/emulsion/termNameDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ mediaOccurrenceArray/itemAvmediaOccurrence/emulsion/termNamei/grank4DAS/physicalOccurrenceArray/itemPhysicalOccurrence/ mediaOccurrenceArray/itemmediaOccurrence/mediaOccurrenceNoteDAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ mediaOccurrenceArray/itemAvmediaOccurrence/mediaOccurrenceNoteDAS/physicalOccurrenceArray/fileUnitPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/mediaOccurrenceNoteDAS/physicalOccurrenceArray/seriesPhysicalOccurrence/ mediaOccurrenceArray/mediaOccurrence/mediaOccurrenceNotei/grank4DAS/onlineResourceArray/onlineResource/descriptioni/grank4DAS/onlineResourceArray/onlineResource/notei/grank4DAS/editStatus/termNamei/grank4DAS/languageArray/language/termNamei/grank4DAS/useRestriction/notei/grank4DAS/functionAndUsei/grank4DAS/numberingNotei/grank4DAS/soundType/termNamei/grank4OBJECTS/seData1I/contentOBJECTS/transcription1I/contentOBJECTS/translation1I/contentNotes:For these fields, copy the data as follows:For archival descriptions – Extract the specified data from all nested digital objects, concatenate it, and copy it to the relevancy field.For digital objects – Extract the specified data only from the appropriate digital object to the relevancy field.Search FieldsAdvanced Search FieldsThe following table describes the fields available for searching on advanced search.Display NameQueryTypeAllowed ValuesRecord Group Number/Collection IDf.recordGroupCollectionId=record-group-number:(${s}) ORhierarchy-item-record-group-number:(${s}) ORcollection-id:(${s}) ORhierarchy-item-collection-id:(${s})stringFree textSearch by Date Range: Fromf.beginDate=${s}stringYYYY-MM-DDSearch by Date Range: Tof.endDate=${s}stringYYYY-MM-DDSearch by Recurring Date: Recurring Datef.recurringDateMonth=${s}stringList of value in a drop-down menu; values are 1–12.Search by Recurring Date: Recurring Datef.recurringDateDay=${s}stringList of value in a drop-down menu; values are 1–31.Search by Exact Date: Exact Datef.exactDate=${s}stringYYYY-MM-DDType of Archival Materialsf.materialsType=${s}stringList of values in the scrollable list box. The list of values is shown in 5.2.1Level of Descriptionsf.level=${s}stringList of values in the scrollable list box. The list of values is shown in 5.2.5File Format of Archival Descriptionsf.fileFormat=${s}stringList of values in the scrollable list box. The list of values is shown in 5.2.6Location of Archival Materialsf.locationIds=${s}stringList of values in the scrollable list box. The list of values is shown in 5.2.7Titlef.allTitles=${s} stringFree textGeographic Referencesf.geographicReferences =subject-reference:(display-name:(${s}) AND @subect-type:TGN)stringFree textCreatorf.creators: (${s})stringFree text Description Identifierf.descriptionIdentifier =naId:(${s}) ORlocalId:(${s}) ORdescription.accession-numbers:(accession-number:(${s}) ) ORdescription.microform-publication:(microform-id:(${s} )) ORdescription.variant-control-number:(variant-number:(${s}) ) ORdescription.rct-numbers:(rct-number:(${s}) ) ORdescription.internal-transfer-numbers:(internal-transfer-number: (${s}) ) ORdescription.record-group-number:(${s}) ORdescription.hierarchy-item-record-group-number:(${s}) ORcollection-id:(${s}) ORhierarchy-item-collection-id:(${s}) stringFree textSearch Fields - Additional InformationDate range field sourcesDate field sources for date range searches include the following:description//productionDateArray/proposableQualifiableDate//logicalDatedescription//broadcastDates//logicalDatedescription//coverageDates/coverageStartDate|coverageEndDate/logicalDatedescription//inclusiveDates/inclusiveStartDate|inclusiveEndDate/logicalDateRecurring date search field sourcesDate field sources for recurring date searches include the following:description//productionDateArray/proposableQualifiableDate/month|daydescription//broadcastDates//month|daydescription//coverageDates/coverageStartDate|coverageEndDate/month|daydescription//inclusiveDates/inclusiveStartDate|inclusiveEndDate/month|dayExact date search field sourcesDate field sources for exact date searches include the following:description//productionDateArray/proposableQualifiableDate//logicalDatedescription//broadcastDates//logicalDatedescription//coverageDates/coverageStartDate|coverageEndDate/logicalDatedescription//inclusiveDates/inclusiveStartDate|inclusiveEndDate/logicalDateType of Archival Materials ValuesType of Archival Material ValueSearch ValueArchitectural and Engineering DrawingsdrawingsArtifactsartifactsData FilesdataFilesMaps and ChartsmapsAndChartsMoving ImagesmovingImagesPhotographs and Other Graphic MaterialsphotographsAndGraphicsSound RecordingssoundTextual RecordstextWeb PageswebLevel of Description ValuesLevel of Description ValueSearch ValueRecord Group recordGroupCollectioncollectionSeries seriesFile fileUnitItemItemFile Format ValuesFile Format ValueSearch ValueTypeASCII Texttext/plaindocumentAudio Visual (Real Media Video Stream)application/vnd.rn-realmediavideoAudio Visual File (AVI)video/x-msvideovideoAudio Visual File (MOV)video/quicktimevideoAudio Visual File (MP4)video/mp4videoAudio Visual File (WMV)video/x-ms-wmvvideoImage (BMP)image/bmpimageImage (GIF)image/gifimageImage (JPG)image/jpegImageImage (JPEG2000)image/jp2imageImage (TIFF)image/tiffimageCompressed File (ZIP)application/zipdocumentMS Excel Spreadsheetapplication/exceldocumentMicrosoft PowerPoint Documentapplication/mspowerpointdocumentMicrosoft Word Documentapplication/msworddocumentMicrosoft Write Documentapplication/mswritedocumentPortable Document File (PDF)application/pdfdocumentSound File (MP3)audio/mpeg3audioSound File (WAV)audio/x-wavaudioWorld Wide Web Pagetext/htmlwebLocation valuesLocation ValueSearch Value(ref-id)William J. Clinton Library1Dwight D. Eisenhower Library2Franklin D. Roosevelt Library3George Bush Library4Gerald R. Ford Library5Gerald R. Ford Museum6Herbert Hoover Library7Harry S. Truman Library8Jimmy Carter Library9John F. Kennedy Library10Lyndon Baines Johnson Library11Richard Nixon Library - College Park12Ronald Reagan Library13National Archives at Boston14National Archives at New York15National Archives at Philadelphia17National Archives at Atlanta18National Archives at Chicago19National Archives at Kansas City20National Archives at Fort Worth21National Archives at Denver22National Archives at Riverside23National Archives at San Francisco24National Archives at SeattleNote: NARA will be moving the records currently assigned to the National Archives at Anchorage reference unit to the National Archives at Seattle by the end of March 2015.National Archives at Seattle26National Personnel Records Center - Civilian Personnel Records27National Personnel Records Center - Military Personnel Records28National Archives at College Park – Cartographic29National Archives at College Park - Motion Pictures30National Archives at College Park - Still Pictures31National Archives at Washington, DC - Textual Reference32National Archives at College Park - Textual Reference33National Archives at College Park – FOIA34Center for Legislative Archives36National Archives at College Park – Electronic Records37Library of Congress, Prints and Photographs Division (an affiliated archives)38National Park Service, Yellowstone National Park Archives (an affiliated archives)39New Mexico Commission of Public Records, State Records Center and Archives (an affiliated archives)40Oklahoma Historical Society (an affiliated archives)41Pennsylvania Historical and Museum Commission, State Archives (an affiliated archives)42United States Military Academy Archives (an affiliated archives)43United States Naval Academy, William W. Jeffries Memorial Archives (an affiliated archives)44Presidential Materials Division48National Archives at St. Louis50Richard Nixon Library51George W. Bush Library53U.S. Government Printing Office (an affiliated archives)54University of North Texas Libraries (an affiliated archives)57Note: NARA pointed out that the Location Value table will be updated in the future, we will need to build the system to handle the case of location value change.Search Results PresentationThis section covers the “brief results” display – the standard output for archival descriptions when shown in the search results.Archival descriptions with digital objects:Archival description without digital objectNote: If the description record has variant control number and the type of the variant control number is “HMS/MLR Entry Number”, the variant control number of the description record will be displayed as HMS Entry Number in this brief result page. IconUse the following algorithm to display the icon:If {I/thumbnailFile} exists, then use:<img src="{I/naid}/opa-renditions/thumbnails/{I/thumbnailFile}"/>Otherwise, use:<img src="{I/iconType}.jpg"/>Metadata FieldsDisplay Rules for HMS Entry Number(s)If there is an HMS/MLR Entry number, display it after the National Archives IdentifierIf there is more than one HMS/MLR Entry number, display the first two HMS/MLR Entry numbers, followed by an ellipse (…) and a commaIf there is no HMS/MLR Entry number at the file unit or item level, display the parent HMS/MLR Entry number(s) as described in 1 and 2 above.LineIndex Fields & Pattern1{I/title}, {I/titleDate}Remove “, “ after {I/title} if {I/titleDate} does not exist.2From RG: {DAS/parent[Record Group]/ recordGroupNumber } OR From: Collection: {DAS/parent[Collection]/ collectionIdentifier } *{DAS/parent[Series]/title} **3{Show highlighted content if available, otherwise show I/teaser}4National Archives Identifier: {I/naId}, Local Identifier: {I/ localIdentifier}, Container ID: {I/containerId}5Creator{s}1: { I/creators }2Note 1: Output “Creator” (if only one creator) or “Creators” (if multiple creators) for the labelNote 2: Separate multiple creators with “;” (semi-colon)* For Series, File Units, and Items, display the parent Record Group Number or Collection Identifier. ** Below the parent Record Group Number or Collection Identifier, display the parent Series title for file units and items. Content Details PresentationThe page layouts for Record group, Collection, Series, File Unit and Item are shown below.Rules for ${online-availability-header}The rules for displaying the “online-availability-header” are as follows:Many times RG, Collections, Series, and File Units are partially digitized so the header is appropriate. But the system should update and remove the header when the entire RG, collection, series, and/or file unit is completely digitized. [Implementation: R2/3]Moderator users can add a specific header for records that are not available online. They can also remove or hide the header. This can be done in the Moderator Workbench where users can edit how this header should look, hide it from view, or remove it entirely, for example: This ${recordType} describes records, some of which may not be available online. To obtain a copy or view the records, please contact or visit the National Archives and Records Administration location(s) listed in the Contact information below.${recordType} is determined by the root tag of the record. The rule is:“Collection” if root tag is <collection>“Record Group” if root tag is <recordGroup>“Series” if root tag is <series>“File Unit” if root tag is <fileUnit>“Item” if root tag is <item>“Item” if root tag is <itemAv>Rules for displaying fieldsThe rules for displaying some fields that appear on the Content Details layouts are shown below. Email addressesWhenever NARA contact information is displayed in the detailed results, all NARA email addresses should be standard links. These links should be displayed in the standard Catalog format and style and should behave in the standard manner when clicked or right-clicked.Record Group{DAS/title}, {DAS/inclusiveDates/inclusiveStartDate + “-“ + DAS/inclusiveDates/inclusiveEndDate}1${online-availability-header}National Archives Identifier:{DAS/naId} DetailsLevel of Description:Record GroupRecord Group Number:{DAS/recordGroupNumber}Contact(s):{for-each: RU =DAS/ referenceUnit,Repeat the following lines:}4{RU/name} {(RU/mailcode)}2, {RU/address1}1{RU/address2}{RU/city}, {RU/state} {RU/postcode}Phone: {RU/phone}3Fax: {RU/fax}3Email: {RU/email}3This record group was compiled or maintained between:{DAS/inclusiveDates/inclusiveStartDate} - {DAS/inclusiveDates/inclusiveEndDate}This record group documents the time period:{DAS/coverageDates/coverageStartDate} -{DAS/coverageDates/coverageEndDate}Date Note:{DAS/dateNote}These records document the following Congresses:{DAS/beginCongress/termName} –{DAS/endCongress/termName }Includes{count(DAS/containsOrderArray)} series described in the catalog 7.2.1 REF _Ref381045238 \r \h 7.2.1{for-each: FA = DAS/findingAidArray/findingAid,repeat the next three rows:}Finding Aid Type:{FA/type}Finding Aid Note:{FA/note}Finding Aid URL:{FA/url/termname}Finding Aid Source:{FA/source}Scope & Content{DAS/scopeAndContentNote}Variant Control NumbersARC Identifier:{DAS/naId}{for-each: VAR = DAS/variantControlNumberArray/variantControlNumber Repeat the following row}{VAR/variant-type}:{VAR/number}{VAR/note}Notes:If field does not exist, remove the preceding commaIf field does not exist, remove the enclosing parenthesisIf field does not exist, remove entire line including the preceding labelRecord Group Link TableThe following table defines the action when the user clicks a link in the full result page of Record Group record.LinkExpected ResultActionIncludes <series-count> series described in the catalogSearch for all Series descriptions with <parent-id> equal to current <naId>. and f.parentNaId ={DAS/naId}&ui.sw={DAS/naId}Search within this Record GroupSearches for all Series, File(s), and Item(s) which are descendants of the current Record Group. Searches for all Series, File(s) and Item(s) which have parent[Level]/naId equal to the current record’s naId.The search parameters are then executed on only that subset of child records and f.ancestorNaIds ={DAS/naId}&ui.sw={DAS/naId}Collection{DAS/title}, {DAS/inclusiveDates/inclusiveStartDate + “-“ + DAS/inclusiveDates/inclusiveEndDate}1${online-availability-header}National Archives Identifier:{DAS/naId} DetailsLevel of Description:CollectionCollection Identifier:{DAS/collectionIdentifier}Contact(s):{for-each: RU =DAS/ referenceUnit,Repeat the following lines:}{RU/name} {(RU/mailcode)}2, {RU/address1}1{RU/address2}{RU/city}, {RU/state} {RU/postcode}Phone: {RU/phone}3Fax: {RU/fax}3Email: {RU/email}3This collection was compiled or maintained between:{DAS/inclusiveDates/inclusiveStartDate} - {DAS/inclusiveDates/inclusiveEndDate}This collection documents the time period:{DAS/coverageDates/coverageStartDate} - {DAS/coverageDates/coverageEndDate}Date Note:{DAS/dateNote}Includes{count(DAS/containsOrderArray)} series described in the catalog 7.3.17.3.1Donor(s):{ for-each: DO = DAS/organizationalDonorArray/organizationName OR DAS/personalDonorArray/person OR DAS/archivalDescriptionsDonorArray/descriptionReference }{DO/termName}7.3.1{ for-each: DAS/findingAidArray/findingAid,Repeat the following three rows}Finding Aid Type:{FA/type}Finding Aid Note:{FA/note}Finding Aid URL:{FA/url/termname}Finding Aid Source:{FA/source}Scope & Content{DAS/scopeAndContentNote}Variant Control NumbersARC Identifier:{DAS/naId}{for-each: VAR = DAS/variantControlNumberArray/variantControlNumber,Repeat the following row:}{VAR/variant-type}:{VAR/number}{VAR/note}Notes:If field does not exist, remove the preceding commaIf field does not exist, remove the enclosing parenthesisIf field does not exist, remove entire line including the preceding labelCollection Link TableThe following table defines the action when the user clicks a link in the full result page of Collection record.LinkExpected resultActionIncludes <series-count> series described in the catalogSearch for all Series descriptions with parent[Level]/naId equal to current naId. and f.parentNaId ={DAS/naId}&ui.sw={DAS/naId}Search within this CollectionSearches for all Series, File(s), and Item(s) which are descendants of the current Collection. Searches for all Series, File(s) and Item(s) which have parent[Level]/naId equal to the current record’s naId.The search parameters are then executed on only that subset of child records. and f.ancestorNaIds ={DAS/naId}&ui.sw={DAS/naId}Donor(s):Links to the specific Authority record who is the Donor based on the donor array type and donor naIdIf donor array type is organizationalDonorArray:${DAS/organizationalDonorArray/organizationName/naId}If donor array type is personalDonorArray:${DAS/personalDonorArray/person/naId}If donor array type is archivalDescriptionsDonorArray:${DAS/archivalDescriptionsDonorArray/descriptionReference/naId}Series{DAS/title}, {DAS/inclusiveDates/inclusiveStartDate + “-“ + DAS/inclusiveDates/inclusiveEndDate}1${online-availability-header}National Archives Identifier:{DAS/naId}Local Identifier:{DAS/localIdentifier}HMS Entry Number(s):{DAS/variantControlNumberArray/variantControlNumber/number}, {DAS/variantControlNumberArray/variantControlNumber/number} (…)2Creator(s){for-each: CO = DAS/creatingIndividualArray/creatingIndividual/ OR DAS/creatingOrganizationArray/creatingOrganization/ }{CO/creator/termName}7.4.1 {(CO/creatorType/termName)}3From:{DAS/parent[Level]/title}7.4.1DetailsLevel of Description:SeriesType(s) of Archival Materials:{for-each: GT = DAS/generalRecordsTypeArray/generalRecordsType}{GT/termName}The creator compiled or maintained the series between:{DAS/inclusiveDates/inclusiveStartDate} - {DAS/inclusiveDates/inclusiveEndDate}note: date qualifier like “ca” shall be includedThis series documents the time period:{DAS/coverageDates/coverageStartDate} - {DAS/coverageDates/coverageEndDate}note: date qualifier like “ca” shall be includedDate Note:{DAS/dateNote}These records document the following Congresses:{DAS/beginCongress/termName} –{DAS/endCongress/termName}Includes{count(DAS/containsOrderArray)} file(s) described in the catalog 7.4.1 REF _Ref381046626 \r \h 7.4.1Other Title(s):{for-each: OT = DAS/otherTitleArray/otherTitle/title}{OT}Function and Use:{DAS/functionAndUse}Scale Note:{DAS/scaleNote}Numbering Note:{DAS/numberingNote}General Note(s):{for-each: GN = DAS/generalNoteArray/generalNote/note}{GN}Arrangement:{DAS/arrangement}Access Restriction(s):{DAS/accessRestriction/status/termName}Specific Access Restriction: {for-each:SAR = DAS/accessRestriction/specificAccessRestrictionArray/specificAccessRestriction }4 {SAR/restriction}, {SAR/restriction} {SAR/securityClassification}, {SAR/securityClassification}Note: {DAS/accessRestriction/accessRestrictionNote}4Use Restriction(s):{DAS/useRestriction/status/termName}Specific Use Restriction: {for-each:SUR = DAS/useRestriction/specificUseRestrictionArray/specificUseRestriction} {SUR/restriction}, {SUR/restriction} Note: {DAS/useRestriction/note}4Custodial History:{DAS/custodialHistoryNote}Transfer Information:{DAS/transferNote}Edited:{DAS/editStatus/termName}Sound Type:{DAS/soundType/termName}Language(s):{for-each: LG = DAS/languageArray/language/termName}{LG}{for-each: FA = DAS/findingAidArray/findingAid Repeat the following three rows:}Finding Aid Type:{FA/type}Finding Aid Note:{FA/note}Finding Aid URL:{FA/url/termname}Finding Aid Source:{FA/source}Accession Number(s):{for-each: AN = DAS/ accessionNumberArray/accessionNumber/number}{AN}Disposition Authority Number(s):{for-each: DAN = DAS/dispositionAuthorityNumberArray/dispositionAuthorityNumber/number}{DAN}Records Center Transfer Number(s):{for-each: RCTN = DAS/recordsCenterTransferArray/recordsCenterTransferMmber} {RCTN}Internal Transfer Number(s):{for-each: ITN = DAS/internalTransferNumberArray/internalTransferNumber/number}{ITN}Microform Publication(s):{for-each: MP = DAS/microformPublicationArray/microformPublication}{MP/identifier}{MP/note}{MP/title}Online Resource(s):{for-each: OR = DAS/onlineResourceArray/onlineResource}{OR/description}7.4.1{OR/note}Subjects Represented in the Archival Material(s):{for-each: SR = DAS/personalReferenceArray/person ORDAS/organizationalReferenceArray/organizationName ORDAS/geographicReferenceArray/geographicPlaceName ORDAS/descriptionReferenceArray/specificRecordsType ORDAS/descriptionReferenceArray/TopicalSubject}{SR/termName}7.4.1Contributors to Authorship and/or Production of the Archival Material(s):{ for-each: CR= DAS/organizationalContributorArray/organizationalContributor ORDAS/personalContributorArray/personalContributor ORDAS/archivalDescriptionsContributorArray/descriptionReference}{CR/termName or CR/title}7.4.1Former Record Group(s):{for-each: FRG = DAS/formerRecordGroupArray/recordGroup}{FRG/recordGroupNumber}Former Collection(s):{for-each: FCL = DAS/formerCollectionArray/collection}{FCL/collectionIdentifier}Scope & Content{DAS/scopeAndContentNote}Variant Control NumbersARC Identifier:{DAS/naId}{for-each: VAR = DAS/variantControlNumberArray/variantControlNumber Repeat the following row}{VAR/variant-type/termName}:{VAR/number}{VAR/note}Archived Copies{for-each: PO = DAS/physicalOccurrenceArray/seriesPhysicalOccurrence}Copy N5:{PO/copyStatus/termName}Extent (Size):{PO/extent}Contact(s):{for-each: RU = DAS/physicalOccurrenceArray/seriesPhysicalOccurrence/ referenceUnitArray/referenceUnit,Repeat the following lines:}{RU/termName} {(RU/mailCode)}3, {RU/address1}1{RU/address2}{RU/city}, {RU/state} {RU/postcode}Phone: {RU/phone}4Fax: {RU/fax}4Email: {RU/email}4Count:{for-each: HM = PO/ holdingsMeasurementArray/holdingsMeasurement}{HM/count}{HM/holdingsMeasurementType/termName}Physical Occurrence Note:{PO/physicalOccurrenceNote}Copy N Media Information:{for-each: MEDIA = PO/mediaOccurrenceArray/mediaOccurrence Repeat the following lines}Specific Media Type: {MEDIA/specificMediaType/termName}4Color: {MEDIA/color}4Container ID: {MEDIA/containerId}4Dimension: {MEDIA/dimension/termName}4Height: {MEDIA/height}4Width: {MEDIA/width}4Depth: {MEDIA/depth}4Media Occurrence Note: {MEDIA/mediaOccurrenceNote}4Physical Restriction Note: {MEDIA/physicalRestrictionNote}4Piece Count: {MEDIA/pieceCount}4Process: {MEDIA/process}4Reproduction Count: {MEDIA/reproductionCount}4Technical Access Requirements Note: {MEDIA/technicalAccessRequirementsNote}4Container List{DAS/physicalOccurrenceArray/SeriesPhysicalOccurrence/containerList}Notes:If field does not exist, remove the preceding commaIf there are less than two variant control numbers, remove the ellipsis and the enclosing parenthesis, only variant control number whose mlr attribute is ”true” will be counted.If field does not exist, remove the enclosing parenthesisIf field does not exist, remove entire line including the preceding labelThe value N should start with 1 and increment by 1 per each occurrenceSeries Link TableThe following table defines the action when the user clicks a link in the full result page of Series record.LinkExpected resultActionCreator(s):Links to the specific Authority record who is the?Creator based on the creator record type and creator-idLinks to the specific Authority record who is the Creator based on creatorType/termName and creator/naIdFrom:Links to the description whose naId is equal to the parent[Level]/naId{for-each: ANCESTOR = DAS/parent[Level] } <file-unit-count/> file(s) described in the catalogSearch for all File descriptions with parent[Level]/naId equal to the current Series naId. andf.parentNaId ={DAS/naId}&ui.sw={DAS/naId}Includes <item-count> file(s) described in the catalogSearch for all Item descriptions with parent[Level]/naId equal to the current Series naId andf.parentNaId ={DAS/naId}&ui.sw={DAS/naId}Search within this SeriesSearches for all File(s), and Item(s) which are descendants of the current Series. Searches for all File(s) and Item(s) which have parent[Level]/naId equal to the current record’s naId. The search parameters are then executed on only that subset of child records. and f.ancestorNaIds={DAS/naId}&ui.sw={DAS/naId}online resource descriptionLinks to online-resource-urlLinks to {DAS/onlineResourceArray/onlineResource /url}Subjects Represented in the Archival Material(s):Links to the specific Authority record who is the Subject based on the subjectType and subjectId${DAS/organizationalReferenceArray/organization/naId} OR${DAS/personalReferenceArray/person/naId}${DAS/descriptionReferenceArray/ descriptionReference/naId}${DAS/geographicReferenceArray/geographicPlaceName/naId}Contributors to Authorship and/or Production of the Archival Material(s):Links to the specific Authority record who is the Contributor based on the contributorRecordType and contributorId${DAS/organizationalContributorArray/organizationName/naId}${DAS/personalContributorArray/person/naId}${DAS/archivalDescriptionsContributorArray/descriptionReference/naId}File Unit{DAS/title}, {DAS/inclusiveDates/inclusiveStartDate + “-“ + DAS/inclusiveDates/inclusiveEndDate}1${online-availability-header}National Archives Identifier:{DAS/naId}Local Identifier:{DAS/localIdentifier}Creator(s){for-each: CO = DAS/creatingIndividualArray/creatingIndividual/ OR DAS/creatingOrganizationArray/creatingOrganization/ }{CO/creator/termName}0 {(CO/creatorType/termName)}3From:{DAS/parent[Level]/title}0if (DAS/variantControlNumberArray/variantControlNumber/variantControlNumberType/termName == “HMS/MLR Entry Number”) {HMS Entry Number(s): {DAS/variantControlNumberArray/variantControlNumber/number}, {DAS/variantControlNumberArray/variantControlNumber/number} (…)2{ for-each: ANCESTOR = DAS/parent[Level]/parent[Level]}{ANCESTOR/title}0DetailsLevel of Description:File UnitType(s) of Archival Materials:{for-each:GT = DAS/generalRecordsTypeArray/generalRecordsType}{GT/general-records-type-desc}The creator compiled or maintained the series between:{DAS/inclusiveDates/inclusiveStartDate} - {DAS/inclusiveDates/inclusiveEndDate}note: date qualifier like “ca” shall be includedThis file documents the time period:{DAS/coverageDates/coverageStartDate} - {DAS/coverageDates/coverageEndDate}note: date qualifier like “ca” shall be includedDate Note:{DAS/dateNote}These records document the following Congresses:{DAS/beginCongress/termName} – {DAS/endCongress/termName }Includes{count(DAS/containsOrderArray)} item(s) described in the catalog 0 REF _Ref381047458 \r \h 0Other Title(s):{for-each: OT = DAS/otherTitleArray/otherTitle/title}{OT}Scale Note:{DAS/scaleNote}Numbering Note:{DAS/numberingNote}General Note(s):{for-each: GN = DAS/generalNoteArray/generalNote}{GN}Arrangement:{DAS/arrangement}Access Restriction(s):{DAS/accessRestriction/status/termName}Specific Access Restriction: {for-each:SAR = DAS/accessRestriction/specificAccessRestrictionArray/specificAccessRestriction }4 {SAR/restriction}, {SAR/restriction} {SAR/securityClassification}, {SAR/securityClassification}Note: {DAS/accessRestriction/accessRestrictionNote}4Use Restriction(s):{DAS/useRestriction/status/termName}Specific Use Restriction: {for-each:SUR = DAS/useRestriction/specificUseRestrictionArray/specificUseRestriction} 4 {SUR/restriction}, {SUR/restriction} Note: {DAS/useRestriction/note}4Custodial History:{DAS/custodialHistoryNote}Transfer Information:{DAS/transferNote}Edited:{DAS/editStatus/termName}Sound Type:{DAS/soundType/termName}Language(s):{for-each: LG = DAS/languageArray/language/termName}{LG}{for-each: FA = DAS/findingAidArray/findingAid }Finding Aid Type:{FA/type}Finding Aid Note:{FA/note}Finding Aid URL:{FA/url/termname}Finding Aid Source:{FA/source}Accession Number(s):{for-each: AN = DAS/accessionNumberArray/accessionNumber/number}{AN}Records Center Transfer Number(s):{ for-each: RCTN = DAS/recordsCenterTransferArray/recordsCenterTransferMmber}{RCTN}Internal Transfer Number(s):{ for-each: ITN = DAS/internalTransferNumberArray/internalTransferNumber/number}{ITN}Microform Publication(s):{ for-each: MP = DAS/microformPublicationArray/microformPublication}{MP/identifier}{MP/note}{MP/title}Online Resource(s):{ for-each: OR = DAS/onlineResourceArray/onlineResource}{OR/description}0{OR/note}Subjects Represented in the Archival Material(s):{for-each: SR = DAS/personalReferenceArray/person ORDAS/organizationalReferenceArray/organizationName ORDAS/geographicReferenceArray/geographicPlaceName ORDAS/descriptionReferenceArray/specificRecordsType ORDAS/descriptionReferenceArray/TopicalSubject}{SR/termName}0Contributors to Authorship and/or Production of the Archival Material(s):{ for-each: CR= DAS/organizationalContributorArray/organizationalContributor ORDAS/personalContributorArray/personalContributor ORDAS/archivalDescriptionsContributorArray/descriptionReference}{CR/termName or CR/title}0Former Record Group(s):{for-each: FRG = DAS/formerRecordGroupArray/recordGroup}{FRG/recordGroupNumber}Former Collection(s):{for-each: FCL = DAS/formerCollectionArray/collection}{FCL/collectionIdentifier}Scope & Content{DAS/scopeAndContentNote}Variant Control NumbersARC Identifier:{DAS/naId}{for-each: VAR = DAS/variantControlNumberArray/variantControlNumber Repeat the following row}{VAR/variant-type}:{VAR/number}{VAR/note}Archived Copies{for-each: PO = DAS/physicalOccurrenceArray/fileUnitPhysicalOccurrence}Copy N5:{PO/copyStatus/termName}Extent (Size):{PO/extent}Physical Occurrence Note:{PO/note}Contact(s):{for-each: RU = DAS/physicalOccurrenceArray/fileUnitPhysicalOccurrence/ referenceUnitArray/referenceUnit orRepeat the following lines:}{RU/termName} {(RU/mailcode)}2, {RU/address1}1{RU/address2}{RU/city}, {RU/state} {RU/postcode}Phone: {RU/phone}4Fax: {RU/fax}4Email: {RU/email}4Count:{for-each: HM = PO/holdings-measurements/holdings-measurement}{HM/measurement-count}{HM/measurement-type}Copy N5 Media Information:{for-each: MEDIA = PO/media-occurrences/media-occurrence Repeat the following lines}Specific Media Type: {MEDIA/mediaType/termName}4Color: {MEDIA/color}4Container ID: {MEDIA/containerId}4Dimension: {MEDIA/dimension}4Height: {MEDIA/height}4Width: {MEDIA/width}4Depth: {MEDIA/depth}4Media Occurrence Note: {MEDIA/mediaOccurrenceNote}4Physical Restriction Note: {MEDIA/physicalRestrictionNote}4Piece Count: {MEDIA/pieceCount}4Process: {MEDIA/process}4Reproduction Count: {MEDIA/reproductionCount}4Technical Access Requirements Note: {MEDIA/technicalAccessN ote}4Container List{DAS/physicalOccurrenceArray/SeriesPhysicalOccurrence/containerList}Notes:If field does not exist, remove the preceding commaIf there are less than two variant control numbers, remove the ellipsis and the enclosing parenthesis, only variant control number whose mlr attribute is ”true” will be counted.If field does not exist, remove the enclosing parenthesisIf field does not exist, remove entire line including the preceding labelThe value N should start with 1 and increment by 1 per each occurrenceDisplay Rules for HMS Entry Number(s)If there is an HMS/MLR Entry number, display it If there is more than one HMS/MLR Entry number, display the first two HMS/MLR Entry numbers, followed by an ellipse (…) If there is no HMS/MLR Entry number at the file unit or item level, display the parent HMS/MLR Entry number(s) as described in 1 and 2 above.File Unit Link TableThe following table defines the action when the user clicks a link in the full result page of File Unit record.LinkExpected ResultActionCreator(s):Links to the specific Authority record who is the?Creator based on the creator-record-type and creator-idLinks to the specific Authority record who is the Creator based on creator/naId and creator typeFrom:Links to the description whose naId is equal to the ancestor naId.{for-each: ANCESTOR = DAS/parent[Level].. } <item-count> file(s) described in the catalogSearch for all Item descriptions with parent naId equal to the current File Unit naId and f.parentNaId ={DAS/naId}&ui.sw={DAS/naId}Search within this FileSearches for all Item(s) which are descendants of the current File. Searches for all Item(s) which have ancestor naId equal to the current record’s naId and f.ancestorNaIds={DAS/naId}&ui.sw={DAS/naId}online resource descriptionLinks to online resource urlLinks to {DAS/onlineResourceArray/onlineResource /url}Subjects Represented in the Archival Material(s):Links to the specific Authority record who is the Subject based on the subject type and subject id${DAS/organizationalReferenceArray/organization/naId} OR${DAS/personalReferenceArray/person/naId}${DAS/descriptionReferenceArray/ descriptionReference/naId}${DAS/geographicReferenceArray/geographicPlaceName/naId}${DAS/topicalSubjectArray/topicalSubject/naId}${specificRecordsTypeArray/specificRecordsType/naId}Contributors to Authorship and/or Production of the Archival Material(s):Links to the specific Authority record who is the Contributor based on the contributor record type and contributor id${DAS/organizationalContributorArray/organizationName/naId}${DAS/personalContributorArray/person/naId}${DAS/archivalDescriptionsContributorArray/descriptionReference/naId}Electronic Records: Download Display IdentifierSome digital objects associated with File Unit descriptions are born-Electronic Records. Some of these are:DAS/variantControlNumberArray/variantControlNumber/number=DDIThe layout for these File Units are identical to that outlined in section 7.5 above with the addition of a list of associated objects presented below the title and above the rest of the record metadata.{DAS/title}, {DAS/inclusiveDates/inclusiveStartDate + “-“ + DAS/inclusiveDates/inclusiveEndDate}1{total number of objects} files availableTechnical Documentation *{for-each object where objects/object/designator="Technical Documentation": Repeat the following lines in numbered/ordered list format based on the value in objects/object@objectSortNum }#. {objects/object/display}** {objects/object/description} ***({objects/object/file@name}, {objects/object/file@mime}, {objects/object/technicalMetadata/file} ****)*****Electronic Records *{for-each object where objects/object/designator="Electronic Records": Repeat the following lines in numbered/ordered list format based on the value in objects/object@objectSortNum }#. {objects/object/display}** {objects/object/description} ***({objects/object/file@name}, {objects/object/file@mime}, {objects/object/technicalMetadata/file} ****)****** Use {designator} to determine whether the object gets displayed under the “Electronic Records” section label or the “Technical Documentation” section label. If there is no {designator} value or any other value, do NOT display a section label, and just list the files.** To determine whether the object is available for display and download, or download only, follow these rules:If objects/object/display=Y or [null], display View/Download.If objects/object/display=N, display Download.*** The link applied to this line is found in objects/object/file@url.**** File size presented in the data is in bytes. This should be converted to KB, MB, or GB and displayed in the UI to the right of the file size.***** In cases where there are more than 10 files for any given section, display a “show all files” link. When clicked, all files are displayed in the UI. Until the link is clicked, only the top 10 file links are displayed.(Record metadata sections begin at this point; please refer to 7.5 for all fields.)Item{DAS/title}: {DAS/subtitle}1, {DAS/inclusiveDates/inclusiveStartDate + “-“ + DAS/inclusiveDates/inclusiveEndDate}2${online-availability-header}National Archives Identifier:{DAS/naId}Local Identifier:{DAS/localIdentifier}Creator(s){for-each: CO = DAS/creatingIndividualArray/creatingIndividual/ OR DAS/creatingOrganizationArray/creatingOrganization/ }{CO/creator/termName}0{(CO/creatorType/termName)}4From:{DAS/parent[Level]/title}0if (DAS/variantControlNumberArray/variantControlNumber/variantControlNumberType/termName == “HMS/MLR Entry Number”) {HMS Entry Number(s): {DAS/variantControlNumberArray/variantControlNumber/number}, {DAS/variantControlNumberArray/variantControlNumber/number}2 (…)3{ for-each: ANCESTOR = DAS/parent[Level]/parent[Level]…}{ANCESTOR/title}0Note: For the header, follow the rules below:1) If there is a production date, this should display. 2) If there are coverage dates, this should display. 3) If there are inclusive dates this should display. DetailsLevel of Description:ItemType(s) of Archival Materials:{for-each:GT = DAS/generalRecordsTypeArray/generalRecordsType/}{GT/general-records-type-desc}This item was broadcast:{for-each:BCD = DAS/broadcastDateArray/proposableQualifiableDate}{BCD}This item’s copyright was established:{for-each:CRD = DAS/copyrightDateArray/proposableQualifiableDate }{CRD}This item was produced or created:{for-each:PDD = DAS/productionDateArray/proposableQualifiableDate }{PDD}This item was released:{for-each:RLD = DAS/releaseDateArray/proposableQualifiableDate }{RLD}The creator compiled or maintained the series between:{DAS/inclusiveDates/inclusiveStartDate} - {DAS/inclusiveDates/inclusiveEndDate}note: date qualifier like “ca” shall be includedThis item documents the time period:{DAS/coverageDates/coverageStartDate} - {DAS/coverageDates/coverageEndDate}note: date qualifier like “ca” shall be includedDate Note:{DAS/dateNote}These records document the following Congresses:{DAS/beginCongress/termName} – {DAS/endCongress/termName}Other Title(s):{for-each: OT = DAS/otherTitleArray/otherTitle/title}{OT}Production Series:{ for-each: PST = DAS/productionSeriesTitle}Title: {PST}5{ for-each: PSST = DAS/productionSeriesSubtitle}Subtitle: {PSST}5{ for-each: PSN = DAS/productionSeriesNumber}Number: {PSN}5Scale Note:{DAS/scaleNote}General Note(s):{for-each: GN = DAS/generalNoteArray/generalNote}{GN}Access Restriction(s):{DAS/accessRestriction/status/termName}Specific Access Restriction: {for-each:SAR = DAS/accessRestriction/specificAccessRestrictionArray/specificAccessRestriction } {SAR/restriction}5, {SAR/restriction}2 {SAR/securityClassification}5, {SAR/securityClassification}2Note: {DAS/accessRestriction/accessRestrictionNote}5Use Restriction(s):{DAS/useRestriction/status/termName}Specific Use Restriction: {for-each:SUR = DAS/useRestriction/specificUseRestrictionArray/specificUseRestriction} {SUR/restriction}, {SUR/restriction}2 Note: {DAS/useRestriction/note}5Custodial History:{DAS/custodialHistoryNote}Transfer Information:{DAS/transferNote}Edited:{DAS/editStatus/termName}Sound Type:{DAS/soundType/termName}Language(s):{for-each: LG = DAS/languageArray/language/termName}{LG}{for-each: FA = DAS/findingAidArray/findingAidRepeat the following 3 rows}Finding Aid Type:{FA/type}Finding Aid Note:{FA/note}Finding Aid URL:{FA/url/termname}Finding Aid Source:{FA/source}Accession Number(s):{ for-each: AN = DAS/ accessionNumberArray/accessionNumber/number}{AN}Disposition Authority Number(s):{ for-each: DAN = DAS/dispositionAuthorityNumberArray/dispositionAuthorityNumber/number}{DAN}7Records Center Transfer Number(s):{ for-each: RCTN = DAS/recordsCenterTransferArray/recordsCenterTransferMmber}{RCTN}Internal Transfer Number(s):{ for-each: ITN = DAS/internalTransferNumberArray/internalTransferNumber/number}{ITN}Microform Publication(s):{ for-each: MP =DAS/microformPublicationArray/microformPublication}{MP/identifier}{MP/note}{MP/title}Online Resource(s):{ for-each: OR = DAS/onlineResourceArray/onlineResource}{OR/description}0{OR/note}Subjects Represented in the Archival Material(s):{for-each: SR = DAS/personalReferenceArray/person ORDAS/organizationalReferenceArray/organizationName ORDAS/geographicReferenceArray/geographicPlaceName ORDAS/descriptionReferenceArray/specificRecordsType ORDAS/descriptionReferenceArray/TopicalSubject}{SR/termName}0Contributors to Authorship and/or Production of the Archival Material(s):{ for-each: CR= DAS/organizationalContributorArray/organizationalContributor ORDAS/personalContributorArray/personalContributor ORDAS/archivalDescriptionsContributorArray/descriptionReference}{CR/termName or CR/title}0Former Record Group(s):{for-each: FRG = DAS/formerRecordGroupArray/recordGroup}{FRG/recordGroupNumber}Former Collection(s):{for-each: FCL = DAS/formerCollectionArray/collection}{FCL/collectionIdentifier}Scope & Content{DAS/scopeAndContentNote}Variant Control NumbersARC Identifier:{DAS/naId}{for-each: VAR = DAS/variantControlNumberArray/variantControlNumber Repeat the following row}{VAR/ type/termName}:{VAR/number}{VAR/note}Archived Copies{for-each: PO = DAS/physicalOccurrenceArray/itemPhysicalOccurrence OR DAS/physicalOccurrenceArray/itemAvPhysicalOccurrence}Copy N6:{PO/copyStatus/termName}Extent (size):{PO/extent}Physical Occurrence Note:{PO/note}Contact(s):{for-each: RU = DAS/physicalOccurrenceArray/itemPhysicalOccurrence/ referenceUnitArray/referenceUnit or DAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ referenceUnitArray/referenceUnit orRepeat the following lines:}{RU/termName} {(RU/mailcode)}4, {RU/address1}2{RU/address2}{RU/city}, {RU/state} {RU/postcode}Phone: {RU/phone}5Fax: {RU/fax}5Email: {RU/email}5Total Footage:{DAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/totalFootage}Total Running Time:{DAS/physicalOccurrenceArray/itemAvPhysicalOccurrence/ totalRunningTime}Copy N6 Media Information:{for-each: MEDIA = PO/media-occurrences/media-occurrence repeat the following lines }Specific Media Type: {MEDIA/mediaType/termName}5Color: {MEDIA/color}5Container ID: {MEDIA/containerId}5Dimension: {MEDIA/dimension}5Height: {MEDIA/height}5Width: {MEDIA/width}5Depth: {MEDIA/depth}5Media Occurrence Note: {MEDIA/mediaOccurrenceNote}5Physical Restriction Note: {MEDIA/physicalRestrictionNote}5Piece Count: {MEDIA/pieceCount}5Process: {MEDIA/process}5Reproduction Count: {MEDIA/reproductionCount}5Technical Access Requirements Note: {MEDIA/technicalAccessNote}5Height: {MEDIA/height}5Emulsion: {MEDIA/emulsion}5Footage: {MEDIA/footage}5Format: {MEDIA/format}5Record Speed: {MEDIA/recordingSpeed/termName}5Reel/Tape/Disc Number: {MEDIA/reelTapeDiscNumber}5Element Number: {MEDIA/elementNumber}5Roll: {MEDIA/rollType}5Running Time: {MEDIA/runningTime}5Soundtrack Configuration: {MEDIA/soundtrackConfig}5Soundtrack Language: {MEDIA/soundtrackLang}5Tape Thickness: {MEDIA/tapeThickness}5Wind: {MEDIA/wind}5Shot List{DAS/shotlist}Notes:If field does not exist, remove the preceding colonIf field does not exist, remove the preceding commaIf there are less than two variant control numbers, remove the ellipsis and the enclosing parenthesis, only variant control number whose mlr attribute is ”true” will be counted.If field does not exist, remove the enclosing parenthesisIf field does not exist, remove entire line including the preceding labelThe value N should start with 1 and increment by 1 per each occurrenceIf item is Unrestricted Electronic RecordsDisplay Rules for HMS Entry Number(s)If there is an HMS/MLR Entry number, display it If there is more than one HMS/MLR Entry number, display the first two HMS/MLR Entry numbers, followed by an ellipse (…) If there is no HMS/MLR Entry number at the file unit or item level, display the parent HMS/MLR Entry number(s) as described in 1 and 2 above.Item Link TableThe following table defines the action when the user clicks a link in the full result page of Item record.LinkExpected ResultActionCreator(s):Links to the specific Authority record who is the?Creator based on the creator type and creatorid${DAS/creatingOrganizationArray/creatingOrganization/creator/naId}${DAS/creatingIndividualArray/creatingIndividual/creator/naId}From:Links to the description whose naId is equal to the ancestor naId{for-each: ANCESTOR = DAS/parent[Level].. } resource descriptionLinks to online resource urlLinks to {DAS/onlineResourceArray/onlineResource /url}Subjects Represented in the Archival Material(s):Links to the specific Authority record who is the Subject based on the subject type and subject id${DAS/organizationalReferenceArray/organization/naId} OR${DAS/personalReferenceArray/person/naId}${DAS/descriptionReferenceArray/ descriptionReference/naId}${DAS/geographicReferenceArray/geographicPlaceName/naId}${DAS/topicalSubjectArray/topicalSubject/naId}${specificRecordsTypeArray/specificRecordsType/naId}Contributors to Authorship and/or Production of the Archival Material(s):Links to the specific Authority record who is the Contributor based on the contributor record type and contributor-id${DAS/organizationalContributorArray/organizationName/naId}${DAS/personalContributorArray/person/naId}${DAS/archivalDescriptionsContributorArray/descriptionReference/naId}Object Metadata PresentationThis section covers the UI presentation of object metadata, Object Designator and Object Description.When an object (types include: image, audio file, video, or PDF) has this data, the Object Designator and Object Description are displayed in a dedicated row below the object viewer and above the object tools, on the left side.Note: If an object of the above types is presented in a UI that does not include a viewer, e.g., a File Unit with Electronic Records/Technical documentation, this data isn’t displayed.These two values are concatenated, separated by a comma and space.{DAS/object/designator}, {DAS/object/description}The UI should display exactly what is returned by the API/data; for example:"num": "5","type": "object","naId": "305300","objects": {"@created": "2015-02-26T12:00:22Z","@version": "OPA-OBJECTS-1.0","object": {"@id": "15021316","@objectSortNum": "9","description": "Forrest, Franklin, George, Greene, Grenada and Hancock Count","designator": "5",If the object, regardless of what type it is, has this data, display as shown in the following mock-ups. If the object doesn’t have this data, the UI appears as it currently appears in PROD R1P1, i.e., no dedicated row.All object viewers display this data in the Content Details page, Preview modal opened in the Results page by clicking on a thumbnail, and the Contributions Workspace.As the user clicks on any navigation element to change from one object to another, the Object Designator/Description text dynamically updates to show the data, if available, for the newly selected object. In cases where there is only one value, it is still displayed in the same position; there is no comma.{DAS/object/designator}OR{DAS/object/description}The UI should display exactly what is returned by the API/data; for example:"num":"1","type":"object","naId":"305300","objects":{"@created":"2015-02-26T12:00:22Z","@version":"OPA-OBJECTS-1.0","object":{"@id":"15021307","@objectSortNum":"1","designator":"COVER",An object with Object Designator and Object Description (the Object Designator field value is 5 and Object Description field value is Forrest, Franklin, George, Greene, Grenada and Hancock Count):An object with Object Designator only (the Object Designator field value is COVER; there is no Object Description field/value):An object without Object Designator and Object Description values (no dedicated row appears): ................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
Related searches
- crossroads financial technologies llc
- crossroads financial technologies reviews
- crossroads financial technologies compl
- crossroads financial technologies sign in
- crossroads financial technologies complai
- crossroads financial technologies complaints
- educational technologies for the classroom
- top 10 emerging technologies 2019
- crossroads technologies amarillo
- crossroads technologies inc
- cross technologies greensboro nc
- new emerging technologies 2019