Home > Mappings

Mappings of EAD to RiC-O and EAC to RiC-O

EAD to RiC-O

A documentation of how the ricoconverter maps EAD 2002 files to RiC-O v0.2 can be read in the Excel file EAD_to_RiC-O_0.2_documentation.xlsx. This mapping table is useful to transition from EAD to RiC-O, but this is not a formal specification and does not document all precise cases.

The precise and formal specifications are given in the form of unit tests in the Unit Tests, under unit-tests/ead2rico.

The following is a list of EAD 2002 elements that RiC-O Converter does not process, because this was considered irrelevant in the RDF world:

  • frontmatter;
  • runner;
  • titlepage.

The following is a list of EAD 2002 elements that RiC-O converter does not process for now, because the Archives nationales de France (ANF) do not use them in their finding aids, or use them very rarely:

  • abbr and expan;
  • abstract;
  • address (in publicationstmt);
  • bioghist (the ANF most often use EAC-CPF files for encoding the biography and history of the agents that created or accumulated the archival fonds);
  • blockquote;
  • chronlist;
  • dao;
  • fileplan;
  • listhead;
  • materialspec;
  • name;
  • phystech;
  • prefercite;
  • sponsor (in titlestmt);
  • table (and its subelements);
  • title.

EAC to RiC-O

A documentation of how the ricoconverter maps EAC-CPF files to RiC-O v0.2 can be read in the Excel file EAC_to_Ric-O_0.2_documentation.xlsx. This mapping table is useful to transition from EAC to RiC-O, but this is not a formal specification and does not document all precise cases.

The precise and formal specifications are given in the form of unit tests in the Unit Tests, under unit-tests/eac2rico.

The ANF use almost all the EAC-CPF elements. However a few elements are not mapped to RiC-O, and not processed by the current version of RiC-O Converter. Let us quote the following ones, that the ANF do not use for now:

Examples

Input (XML) example files can be found under input-ead and input-eac.