RA EAD english version
EAD elements and the corresponding presentation in the search service.
Example file 1 (SE/ULA/10012/A I/1)
Example file 2 (SE/KrA/0414/0028/0006)
<filedesc>
<titlestmt>
<titleproper>5. Mariaeburgum. Ichnographice De Scriptum. A 1639. Tabula Explicans. [Marienburg/Malbork]</titleproper>
</titlestmt>
</filedesc>
and
<did>
<unittitle>5. Mariaeburgum. Ichnographice De Scriptum. A 1639. Tabula Explicans. [Marienburg/Malbork]</unittitle>
...
</did
<eadheader ...>
<eadid countrycode="SE" mainagencycode="ULA">SE/ULA/10012/AI/1</eadid>
...
</eadheader>
The reference is actually SE/ULA/10012/A I/1, but the blank is omitted in the element content.
<did>
<unitid countrycode="SE" repositorycode="ULA">1</unitid>
...
</did>
<physdesc encodinganalog="3.4.4">
<extent unit="Kartor">1</extent>
</physdesc>
<did>
...
<unitdate calendar="gregorian" era="ce" normal="1752/1764" encodinganalog="3.1.3">1752--1764</unitdate>
The unitdate element's text content is unstructures, there can be a qualifying explanation for example ("osäker", uncertain in swedish). If the archival record has an unambiguous year in the date fileld, the attribute normal will contain a standard representation of the time or time span YYYY[/YYYY].
<accessrestrict encodinganalog="3.4.1">
<p>Delvis</p>
</accessrestrict>
The two first elements of the reference code denotes the archival institution. In the example SE/ULA = Landsarkivet i Uppsala.
<origination encodinganalog="3.2.1">
<name authfilenumber="SE/902002">Lokal upphovsman KARTIA (KrA) - Getkant, Friedrich</name>
</origination>
<scopecontent encodinganalog="summary">
<p>Med ortregister.</p>
</scopecontent>
<userestrict encodinganalog="3.4.5" type="dao">
<p>
<extref xlink:href="https://creativecommons.org/publicdomain/zero/1.0/">CC0</extref>
</p>
</userestrict>
<altformavail>
<p>Mediatyp enligt Kartia: Mikrofilm Mediatyp enligt Kartia: K 011 Mediatyp enligt Kartia: 471 </p>
</altformavail>
<revisiondesc>
...
<change>
<date calendar="gregorian" era="ce">2021-11-18T13:53:13.173Z</date>
<item>Senaste uppdatering i Arkis</item>
</change>
</revisiondesc>
Example file (SE/ULA/10012/A I)
EAD data for a series record has the same basic construction as for a volume. Data for the volumes in the series are then listed as elements nested under
<dsc type="othertype">
...
</dsc>
<c level="otherlevel" otherlevel="volym" id="d2e101" encodinganalog="3.1.4">
<did>
<unitid encodinganalog="3.1.1" type="call number">SE/ULA/10012/A I/2</unitid>
<unittitle>1772--1778</unittitle>
<unitdate calendar="gregorian" era="ce" normal="1772/1778" encodinganalog="3.1.3">1772--1778</unitdate>
<dao xlink:role="IMAGE" xlink:href="https://sok-acc.riksarkivet.se/bildvisning/C0002788?partner=ape" />
</did>
<scopecontent encodinganalog="summary">
<p>Med ortregister.</p>
</scopecontent>
<accessrestrict encodinganalog="3.4.1">
<p>Delvis</p>
</accessrestrict>
<otherfindaid encodinganalog="3.4.5">
<p>
<extref xlink:href="https://sok-acc.riksarkivet.se/arkiv/4MgUgjX9rH6cxG02H087k3">Post i NAD</extref>
</p>
</otherfindaid>
</c>
EAD data for a fonds record also use the same basic construction. Series in the fonds record are listed as elements under
<dsc type="othertype">
...
</dsc>
Note that the volumes in turn are nested under the series elements.
<c level="series" id="d2e101">
<did>
<unitid countrycode="SE" repositorycode="ULA">A I</unitid>
<unittitle>Husförhörslängder</unittitle>
</did>
<accessrestrict type="Delvis">
<note>
<p>Delvis</p>
</note>
</accessrestrict>
<c level="otherlevel" otherlevel="volym" id="d2e102">
<did>
<unitid countrycode="SE" repositorycode="ULA">2</unitid>
<unitdate type="inclusive">1772--1778</unitdate>
</did>
<odd>
<p>Med ortregister.</p>
</odd>
<accessrestrict type="Delvis">
<note>
<p>Delvis</p>
</note>
</accessrestrict>
</c>
...
</c>
