|
The new 1.6.1 Schema is ready for
release has been deployed in both the Operational and Practice Registries.
Aside
form the enhancements in functionality inside the DTIC
Portal,
you will notice:
- the inclusion of three
new metadata fields in the schema
- the modification of a registry
operation
- a new search field.
The three metadata fields introduced are 'repositoryIdentifier', 'secondaryContentLocation'
and a new "collection" element at the LOM level. Of these fields only the
repositoryIdentifier and the collection are mandatory and indexed. The
secondaryContentLocation is a placeholder field for the upcoming release 1.7
that should introduce new multiple location functionality. If you in fact have
secondary locations for a particular content object you can start submitting
this information, but the field is not mandatory and you could just disregard it.
The repositoryIdentifer field is destined to help users identify
the relationship of particular content with its respective repository. This
field is mandatory,
so if you are creating metadata instances about a particular content object,
please make sure you know its content object repository ID prior to registering it. You can obtain this
information by querying the registry for the content object you intend to add
metadata instances to. As a general change,
whenever you register a
new repository from now on you will receive a repository ID that should be included with any metadata registered
about content in that repository.
The collection element now available as a new classification item
is required to at least have the value "DOD".
This is an open vocabulary field that will allow users to include their own
collection definitions along with their metadata instances. This will also allow
the inclusion of metadata instances that catalog content objects into ad hoc
collections. An example of the
default required value is as follows:
<lom:classification>
<lom:purpose>
<lom:source>ADL-Rv1.0</lom:source>
<lom:value>collection</lom:value>
</lom:purpose>
<lom:taxonPath>
<lom:source>
<lom:string>ADL/DOD Content Category Taxonomy</lom:string>
</lom:source>
<lom:taxon>
<lom:entry>
<lom:string>DOD</lom:string>
</lom:entry>
</lom:taxon>
</lom:taxonPath>
</lom:classification>
We have also modified the update operation as a result of these new
fields. The UPDATE operation is now a total overwrite operation. This implies,
the operation would now update 'envelope', and 'LOM'. If
the registry is delegated the responsibility of content object handle
administration, the operation would also modify the content location in
the content object handle. Therefore make sure you include all the required
fields for
update operations.
Additionally please notice that HTTP GET support
is now included for requests,
namely, Registry Query, Registry Transaction Status, and
Registry Validation Status, in addition to Registry LOM retrieval and
Registry Metadata Instance Information retrieval.
Finally as part of the searchable fields
we have incorporated a new index field named 'defaulttext'. This field catches
(and therefore indexes) all XML elements for which there are no indexing rules.
This means that a query for items in text: AND defaulttext: can now successfully
query all content in the registry incorporating both fielded and unfielded
elements of the metadata.
As usual you can find the latest adl registry schemas described on
the ADL-R portal at:
https://adlregistry.dtic.mil/5/index1.htm
You can also access the ADL-R
schemas at
http://hdl.cordra.net/2000.2.1/ADL-R-Reg-T
and the ADL LOM schema at:
http://hdl.cordra.net/2000.2/adlreg-lom
|
