Articulation with RiC: specific attributes

[BrigitteMichel]

Creator of issue

1. Brigitte Michel ([email protected])
2. Abes (Agence bibliographique de l'enseignement supérieur = Bibliographic Agency of Higher Education)

The issue relates to

• EAC-CPF schema issue
• EAC-CPF Tag Library issue
• EAD schema issue
• EAD Tag Library issue
• Schema issue
• Tag Library issue
• Suggestions for all schemas
• Suggestions for all Tag Libraries
• Other

Wanted change/feature 1

• Text: EAD 4.0 must facilitate conversions in both directions EAD 4.0 <-> RiC-O for institutions like Abes that will need to perform multiple XML-EAD4.0 <-> RiC-O conversions on a recurring, case-by-case basis over several years, depending on data exposure modes, network member institutions, and utilization by various partners.
• To achieve this, it would be beneficial to define specific attributes in EAD 4.0 dedicated to RiC, which would ease repeated two-way conversions without requiring everything to be systematically recalculated.
• We have identified two recurring needs:
  • An attribute that allows encoding, for a given XML element, at least the corresponding entity as defined by RiC. The creation of an additional attribute beyond the existing @localType is justified by the international normative character of RiC, and the fact that an institution may have both local or national typology needs and a requirement to link to an RDF RiC-O base. This would also allow:
    • The author of the EAD instance to specify within a <c> if the institution considers it to be a RiC-E03 Record Set, a RiC-E04 Record, or a RiC-E05 Record Part (see example line 119: decision to make each letter a record).
    • Given the variability from one institution to another, and one IR to another, it is very difficult to define universal conversion rules, especially in collective bases (often an overlooked aspect in current experiments). This information cannot systematically be inferred from the value of @level.
    • Determining a priori if an XML element concerns the record entity or the instantiation entity (see <scopeContent> in the example).
  • An attribute that records the identifier assigned by the entity-relations base to the corresponding RiC entity for the XML-EAD4 element, to facilitate updates and successive passes, such as for example @ricTargetId. It seems preferable to have a distinct, unambiguous attribute separate from @id or @target, which primarily aim at internal EAD 4.0 relations.
• These two attributes could accommodate data conforming either to RiC-CM, if still theoretical (as in the example), or to RiC-O if the institution manages an RDF base.

Wanted change/feature bis

• Text: An alternative, more comprehensive but rigorous solution would be to define five attributes.
  • Instead of a single attribute @ricType, define:
    • @ricEntity for correspondence to an entity
    • @ricRelation for correspondence to a relation
    • @ricAttribute for correspondence to an entity attribute
  • Instead of a single attribute @ricTargetId, define:
    • @ricEntityId for the identifier of the entity concerned by the EAD element
    • @ricTargetEntityId for the target of the relation when it exists

Suggested Solution

• Text: Minimum Proposal: Create two optional attributes, @ricType and @ricId, for all cases where these cannot be inferred from the element itself: <c> for the type of record, elements that can equally concern a record entity, or an instantiation entity (e.g., <accessConditions>, <processInfo>, etc.).
• Maximalist Proposal: Create five optional attributes (see above) in nearly all elements. The example follows the maximalist proposal.

[BrigitteMichel]

Example :

<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="https://raw.githubusercontent.com/SAA-SDT/eas-schemas/release_2024_03/xml-schemas/ead/ead.nvdl" type="application/xml" schematypens="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"?>
<?xml-model href="https://raw.githubusercontent.com/SAA-SDT/eas-schematrons/release_2024_03/schematron/ead.sch" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>
<!-- =========================================================================
Example ticket 150       Attribtues RiC
========================================================================= -->
<ead xmlns="https://archivists.org/ns/ead/v4" xmlns:xhtml="http://www.w3.org/1999/xhtml">
	<control languageEncoding="iso639-2" countryEncoding="iso3166-1" dateEncoding="iso8601"
		repositoryEncoding="iso15511" scriptEncoding="iso15924" coverageEncoding="EASList"
		levelEncoding="EASList" maintenanceEventTypeEncoding="EASList"
		maintenanceStatusEncoding="EASList" physDescStructuredTypeEncoding="EASList"
		contactLineTypeEncoding="EASList" audienceEncoding="EASList" detailLevelEncoding="EASList"
		descriptionOfComponentsTypeEncoding="EASList" publicationStatusEncoding="EASList"
		statusEncoding="EASList" unitDateTypeEncoding="EASList" detailLevel="extended"
		maintenanceStatus="new" publicationStatus="inProcess">

		<recordId>FR-751063002-4703</recordId>
		<otherRecordId valueURI="" ricEntity="RiC-E02" ricEntityId="recordSet8742651"/>
		<maintenanceAgency countryCode="FR" vocabularySource="Repertoire_des_Centres_de_Ressources" ricEntity="RiC-E11" ricEntityId="84552144752" ricRelation="RiC-R038" ricTargetId="recordSet8742651">
			<!-- @vocabularySource @vocabularySourceURI @valueURI -->
			<agencyCode>FR-341725201</agencyCode>
			<otherAgencyCode/>
		</maintenanceAgency>

		<maintenanceHistory> [...]
			<maintenanceEvent maintenanceEventType="updated" id="event2" ricEntity="RiC-E14" ricEntityId="Event56" ricRelation="RiC-R059" ricTargetId="recordSet8742651">
				<agent ricEntity="RiC-E13" ricRelation="RiC-R060" ricTargetId="recordSet5443611">
					<agentName>ScriptRicoToEAD4</agentName>
					<agentType>machine</agentType>
				</agent>
				<eventDateTime standardDateTime="20240430"/>
				<eventDescription>Ajout des identifiants des données converties en RiC</eventDescription>
			</maintenanceEvent>
		</maintenanceHistory>
		<conventionDeclaration id="otherLevelEncoding"
			vocabularySource="Bonnes Pratiques de l'EAD en Bibliothèques"
			valueURI="https://www.ead-bibliotheque.fr/guide/organisation-description/level/" ricEntity="RiC-E16" ricEntitytId="rule11" ricRelation="RiC-R063" ricTargetId="recordSet8742651">
			<reference>Bonnes pratiques de l'EAD en Bibliothèques : niveaux de description
				archivistique</reference>
			<shortCode>BPEAD_date</shortCode>
			<descriptiveNote>
				<p>Les bonnes pratiques de l'EAD en Bibliothèques recommandent l'utilisation des
					valeurs suivantes de level : pour les fonds d'archives, fonds, collection,
					series, file, recordgrp, item (issus de la liste EAS) ; pour les manuscrits
					unitaires, document_unitaire, document_composite, recueil_factice,
					subdivision_matérielle, subdivision_intellectuelle.</p>
			</descriptiveNote>
		</conventionDeclaration> [...]
		<localTypeDeclaration id="indexationType" ricEntity="RiC-E16" ricTargetId="rule584">
			<reference>Types de points d'accès</reference>
			<shortCode>indexationType</shortCode>
			<descriptiveNote>
				<p>Cette liste contrôlée permet de différencier les différents types d'entités
					indexées : persName, famName, corpName, title.</p>
				<p>Faute d'attribut @role, les types sont suivis du code de rôle pour cet encodage.
					Exemple : persname_0070 pour l'auteur du texte.</p>
			</descriptiveNote>
		</localTypeDeclaration>[...]
		<rightsDeclaration valueURI="https://www.etalab.gouv.fr/licence-ouverte-open-licence/" ricEntity="RiC-E16" ricTargetId="rule001">
			<reference>Licence ouverte de l'État</reference>
			<shortCode>etalab-2.0</shortCode>
			<descriptiveNote>
				<p>Cet instrument de recherche publié par la Bibliothèque nationale de France est
					placé sous licence ouverte de l'État (licence etalab 2.0). La réutilisation
					gratuite ou commerciale est autorisée sous réserve de la mention de la
					source.</p>
			</descriptiveNote>
		</rightsDeclaration>
	</control>
	<archDesc level="fonds" ricEntity="RiC-E02" ricEntityId="recordSet8742651">
		<identificationData>
			<unitId localTypeDeclarationReference="BPEAD_unitid" localType="cote" countryCode="FR"
				repositoryCode="751069804">Fonds Berger</unitId>
			<unitTitle>Papiers Philippe Berger</unitTitle>
			<unitDate calendar="gregorian" era="" standardDate="1846/1912">1846-1912</unitDate>
			<languageOfMaterial>
				<language languageCode="fre">français</language>
			</languageOfMaterial>
			<legalStatus ricAttribut="RiC-A26" ricTargetId="recordSet8742651">
				<term>Document patrimonial</term>
				<term>État</term>
			</legalStatus>
		</identificationData>
		<agents>
			<agent>
				<agentName vocabularySource="IdRef" valueURI="http://www.idref.fr/03357457X/id" ricEntity="RiC-E08" ricEntitytId="agent03357457X" ricRelation="RiC-R063" ricTargetId="recordSet8742651">Berger, Philippe (1846-1912)</agentName>
				<agentRole localTypeDeclarationReference="Calames_roles" localType="producteur" ricEntitytId="03357457X" ricRelation="RiC-R026i" ricTargetId="recordSet8742651"/>
			</agent>
<!--Alternative --->
			<agent ricEntitytId="03357457X" ricEntity="RiC-E08" ricEntitytId="agent03357457X" ricRelation="RiC-R026i" ricRelation="RiC-R063" ricTargetId="recordSet8742651>
				<agentName vocabularySource="IdRef" valueURI="http://www.idref.fr/03357457X/id">Berger, Philippe (1846-1912)</agentName>
				<agentRole localTypeDeclarationReference="Calames_roles" localType="producteur"/>
			</agent>
		</agents>
		<accruals ricAttribut="RiC-A01" ricTargetId="recordSet8742651">
			<p>Fonds clos</p>
		</accruals>
		<biogHist ricEntity="RiC-E08" ricAttribut="RiC-A21" ricTargetId="03357457X">
			<p>Philippe Berger (1846-1912) entre en 1867 à la Faculté de théologie protestante de
				Strasbourg, où il fait la connaissance d'Ernest Renan et commençe l'apprentissage de
				l'hébreu. Engagé dans le service de santé de l'armée de la Loire pendant la guerre
				de 1870, il est décoré de la médaille militaire pour sa conduite lors du siège de
				Paris. En 1874, il est nommé à la bibliothèque. Professeur d'hébreu à la faculté de
				théologie protestante de Paris en 1877, il succéde en 1893 à Renan au Collège de
				France, où il occupe la chaire d'hébreu jusqu'en 1910. En 1892 il est élu à
				l'Académie des inscriptions et belles-lettres. Entré en politique en 1895, il est
				sénateur du Haut-Rhin de 1904 à 1912.</p>
		</biogHist>
		<sourceOfAcquisition>
			<p>Legs de Philippe Berger.</p>
		</sourceOfAcquisition>
		[...]
		<descriptionOfComponents>
			<c level="file" ricEntity="RiC-E03" ricTargetId="recordSet954422444">
				<identificationData>
					<unitTitle>Correspondance de Philippe Berger</unitTitle>
					<unitDate calendar="gregorian" era="" standardDate="1846/1912"
						>1846-1912</unitDate>
				</identificationData>
				<c> [...]

					<c level="item" ricEntity="RiC-E02" ricEntityId="record587452212555">
						<identificationData>
							<unitTitle>Lettre d'Antoine Abbadie</unitTitle>
							<physDesc ricEntity="RiC-E06" ricEntityId="InstanceRecord587452212555Inst1">
								<quantity>1</quantity>
								<unitType>bifeuillet</unitType>
							</physDescStructured>
						</identificationData>
						<scopeContent>
							<p ricattribut="RiC-A03" ricTargetId="record587452212555">Une lettre autographe signée.</p>
							<pricattribut="RiC-A05" ricTargetId="InstanceRecord587452212555Inst1">Dans une enveloppe timbrée</p>
						</scopeContent>
					</c>
				</c>
		</descriptionOfComponents>
	</archDesc>
</ead>

[kerstarno]

Might be discussed by TS-EAS during their meeting on 12/13 August 2024 if time allows (i.e. if other discussion points can be solved in less time than anticipated. Otherwise, the EAD team will pick this up at their next monthly meeting end of September.

[kerstarno]

As a note:

• TS-EAS cannot by itself define a mapping between one (or all) of the EAS and any other standard. This should always happen in collaboration with the committee responsible for the other standard in question. There have been conversations between TS-EAS and EGAD members about an official crosswalk between EAD (and EAC-CPF and, potentially, EAC-F) and RiC, but this does not exist yet, which would make it difficult to unilaterally decide about EAD 4.0 elements where the suggested attributes should become available.
• The EAS have relations to several other standards, not only RiC (respectively the previous ICA standards). Defining specific attributes for RiC, but not for other standards would hence be questionable, even if these attributes would be optional.
• EAD 4.0 introduces the option to add attributes from other namespaces to any element of EAD. This might be an alternative option for those who would want to indicate these relations between EAD elements and RiC entities and attributes (especially when this refers to RiC-O).

[kerstarno]

Not discussed eventually during the TS-EAS meeting on 12/13 August due to time constraints. Will now be on the agenda at the EAD team meeting either in September or October 2024.