Date: Thu, 28 Mar 2024 07:41:39 -0400 (EDT)
Message-ID: <1008232907.27574.1711626099374@lyrasis1-roc-mp1>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_27573_1193128543.1711626099374"
------=_Part_27573_1193128543.1711626099374
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Fedora supports ingest of objects in a Fedora-specific extension=
of Metadata Encoding and Transmission Standard (METS). More information on=
METS can be found at http://www.loc.gov/standards/mets/. =
For specific information about the Fedora extension to METS, please see the=
Fedora METS 1.1 schema.
Since METS was designed to be very generic and support a variety of uses=
, the rules of the METS Schema are very general-purpose. Fedora objects mus=
t conform to other rules that are beyond the scope of what is expressed in =
the METS schema. Therefore, the Fedora Object XML submissions will also be =
validated against a set of Fedora-specific rules that are expressed using t=
he Schematron language. Internally, the repository will use Schematron to e=
nforce these rules on incoming XML submission packages. The Schematron rule=
s are expressed in XML and can be found in the Fedora server distribution a=
t: %FEDORA_HOME%\server\schematron\metsExtRules1-1.xml
.
As usual an example is worth a thousand words. So, please refer to this sample Fedora object that=
is encoded for ingest in METS 1.1.
For convenience and ease of understanding we have enumerated the Fedora =
rules in plain English below.
On this page:
General attributes
- On METS root element, the OBJID attribute will represent the Fedora obj=
ect PID. Normally, this should be left empty so that the Fedora repository =
can generate a new PID. However, you can assign test/demo PIDs by inserting=
a value in OBJID that begins with "demo:" or "test:" for example, "demo:10=
0"
- On METS root element, the value of the EXT_VERSION attribute must be "1=
.1".
- On METS root element, the value of LABEL serves as the official descrip=
tion of the object. If there is no Dublin Core record present in the object=
, the Fedora repository will use this label to populate the title element o=
f a baseline Dublin Core record for the object.
- On METS root element, the PROFILE element can be used by institutions t=
o classify different types of Fedora data objects.
- On the METS:metsHdr element the CREATEDATE attribute should be omitted =
since the Fedora repository will assign this at ingest time. Fedora dates a=
re in the ISO 8601 format in milliseconds and with UTC time as follows: yyy=
y-MM-ddTHH:mm:ss.SSSZ. The same thing goes for LASTMODDATE.
- On the METS:metsHdr element the RECORDSTATUS should be set to "A", "I",=
or "D" to indicate that the object is in the "Active", "Inactive", or "Del=
eted" state. The usual state is "A" (Active). These states may be used by p=
olicy enforcement, for example, to prevent access to items in non-Active st=
ates. They may also be used by external tools, for example, to indicate whe=
ther an object's data should be indexed or not.
Datastreams
- To create a proper section for Datastreams in the METS file, the METS:f=
ileSec must have a single child METS:fileSec element whose ID attribute has=
the value "DATASTREAMS"
- Datastreams that are encoded in the METS:fileSec must follow the follow=
ing pattern to establish proper version groups and datastream IDs. Each dat=
astream has its own METS:fileGrp whose ID attribute is the official datastr=
eam ID. The recommended convention is ID=3D"DSn" where n is a number (for e=
xample ID=3D"DS1" or ID=3D"DS2)."
- Within a METS:fileGrp, there can be one or more METS:file elements to r=
epresent different versions of a datastream. As of Fedora 1.2, versioning o=
f data objects is supported. The METS:file element for the datastream must =
have and ID attribute that represent the version number relative to the dat=
astream ID set in the METS:fileGrp. The recommended convention is ID=3D"DSn=
.v" where n is the number of the datastream and v is the version number (fo=
r example ID=3DDS1.0 or ID=3DDS1.1).
- The METS:file element for a datastream must have a MIMETYPE.
- The METS:file element for a datastream must have an OWNERID attribute. =
In Fedora, the OWNERID attribute is used to encode the Datastream Control G=
roup. The following are valid values:=20
- "M" - Managed Content. This tells the repository to store the datastrea=
m's content byte stream inside the repository. When the METS:file contains =
"M" on the OWNERID, the repository will resolve the URL associated with the=
METS:file element and pull the content into the repository for permanent s=
torage. Fedora will establish its own local identifier for retrieving the c=
ontent, and disregard the original URL that came in on the METS submission =
package.
- "E" - External Referenced Content. This tells the repository to store t=
he URL for the datastream content, not the content byte stream itself. For =
this type of datastream, Fedora does not actually manage or have custodians=
hip of the content, but it manages the link to the content and some basic m=
etadata about it.
- "R" - Redirected Content. Like "E" this tells the repository to store t=
he URL for the datastream content, not the content byte stream itself. More=
importantly, it tells the repository not to mediate or proxy this content =
at runtime. Instead, the repository will redirect to the URL at run time. T=
his is desirable when a datastream points to a streaming media source, or t=
o a complex web page where some components are lost during proxying.
Inline XML Datastreams
- Datastreams can also be encoded in the METS:dmdSecFedora and METS:amdSe=
c. These are considered "inline XML datastreams" in Fedora. The METS:dmdSec=
Fedora and METS:amdSec elements act as datastream version group containers =
just like the METS:fileGrp acts for regular datastreams. Within these eleme=
nts, the METS "metadata section" elements (i.e., METS:techMD, METS:rightsMD=
, etc.) are used for the specific version instances of the inline metadata =
datastreams, just like the METS:file acts for regular datastreams. The data=
stream IDs work the same way, where the ID attribute on the container eleme=
nt acts as the datastream ID, and the ID on the metadata section element ac=
ts as the datastream version ID.
- Do not use the schemaLocation attribute in the root element of inline X=
ML datastreams (within METS:mdWrap element).
Dublin Core Record Datastr=
eam
- A Dublin Core (DC) record is optional in the Fedora object submission p=
ackage. If one is not provided the repository will automatically create a m=
inimal DC record in the object by using the LABEL (on METS root) as the DC =
title element. It will also use the object PID as the DC identifier element=
.
- If a DC record is provided in the METS submission package it should be =
encoded within a METS:dmdSecFedora. The dmdSecFedora element will act as th=
e datastream version group container. It MUST have an ID attribute whose va=
lue is "DC" to be recognized by Fedora!
- Within the METS:dmdSecFedora, there must be one METS:descMD element. Th=
is element is part of the Fedora extension of METS 1.1 and is used to encod=
e a specific version of the DC datastream within the version group containe=
r. The ID attribute on the METS:descMD element MUST have the value "DC1.0" =
to be recognized by Fedora.
- The actual DC metadata should be encoded using the Open Archives Initia=
tive (OAI) Dublin Core schema.
------=_Part_27573_1193128543.1711626099374--