ADL Registry

• Search
• Contribute
• Getting Started

• Register Repository/Contributors
• Technical Reference
• About ADL Registry
• Practice Registry

• Home
• Getting Started

Getting Started

Getting Started content is intended to provide help for all audiences interested in learning about the ADL Registry, its functions, and its features.

Click on the appropriate link for more Getting Started information by topic area.

 

Searching the ADL Registry for Digital Objects (back to top)

Click Search or Advanced Search if you are ready to perform a search now.

The ADL Registry search functions enable public access to the metadata contained in the Registry. Access to the digital objects described by the metadata is controlled by the local repository and may require an access account.

Performing Advanced Searches

Click Advanced Search if you are ready to perform a search now. In addition to searching Title, Description, and/or Keyword, you may alternatively search all Metadata Elements, including:

Contributor Name Contributor Role Contributor Entity Contributor Date Location Title Description Keyword Version Number Unique ID

Content Status Creation Date Collection Copyright Restriction Security Level Distribution Restriction Content Type Formatting Standard MIME Type/Format

Content Object ID Metadata Instance ID Metadata Schema Technical Format Conformance Categorization Repository ID

Performing Wildcard Searches

Complex queries, including wildcard searches are available for single character and multiple character string wildcards.

Wildcard	Meaning	Usage	Result
?	The ? symbol replaces a single character in a string of characters. ? cannot be used as the first character in the string.	device? d?vice	device, devices device
*	The * symbol replaces multiple characters in a string of characters. * cannot be used as the first character in the string.	improv*	improve, improvised

 

Retrieving Search Results

The results of a search will display an initial set of data elements. From Search Results, you can:

• Get digital object: this resolve to the location provided in the metadata
• View metadata: this will display the entire set of metadata included in the transaction (the ADL Registry displays only the mandatory LOM elements)
• Download the complete metadata record as an XML file

Registering Your Repository with the ADL Registry (back to top)

Click to begin the Repository Registration process. In order to contribute metadata to the ADL Registry, you must first register your repository and then register contributors.

Following the successful submission of the Repository Registration form, the Repository Manager will receive an email from adlregistry@adlnet.gov with approval and namespaces for both the ADL Registry and Practice ADL Registry. Following that, the Repository Manager will receive an email from adlrhelpdesk@adlnet.gov containing repository namespaces, identifiers, and group handles for the ADL Registry and Practice ADL Registry. Initially, access will only be granted for the Practice ADL Registry. After actively participating in the Practice ADL Registry, the Repository Manager will need to contact the Registrar at adlregistry@adlnet.gov to activate the (operational) ADL Registry account. After registering the repository, the Repository Manager is given the opportunity to register as a contributor for the repository.

Repository Managers

The Repository Manager is the primary point of contact for the repository that is registered with the ADL Registry. Generally, the Repository Manager is assigned rights to insert, update, activate, search, deactivate, delete, withdraw, and move. The Repository Manager is responsible for the operation, maintenance, access, security, and business rules for the local repository. Through delegation to specific contributors, the Repository Manager is also responsible for creating and maintaining metadata records that describe digital objects in the repository. If local security and access policies prevent direct access to identified digital objects, the Repository Manager is required to document how digital objects may be obtained.

Local Digital Object Repositories

A digital object repository is a local system for storing, maintaining, and accessing digital objects. While no specific implementation is assumed, certain capabilities are required to comply with the ADL Registry model. These include:

• A means to create, register, and maintain digital object metadata records in the ADL Registry
• A means to electronically access registered content objects within the repository
• Approval to participate in the ADL Registry by the appropriate DoD Component Proponent

A local repository applying for an account with the ADL Registry must be approved by the appropriate DoD Component Proponent.

Registering Contributors for Registered Repositories (back to top)

Click to begin the Contributor Registration process. In order to contribute metadata to the ADL Registry, you must first register your repository and then register contributors.

Generally, a contributor is assigned rights to insert, update, activate, search, and deactivate metadata. When registering as a contributor, the Repository ID and Repository Manager information will be required from the registered repository for which you want to contribute metadata. Following the successful submission of the Contributor Registration form, the Repository Manager will be contacted and access rights for the new contributor will be requested. When the account is approved, the contributor will receive an email from adlrhelpdesk@adlnet.gov containing Username and temporary Password and will be prompted to use the Change/Retrieve Password function available from the ADL Registry web site.

Contributing Content to the ADL Registry (back to top)

All digital object metadata contributed to the ADL Registry is persistent and accessible. Only the authorized contributing repository may make changes to the digital object metadata.

The ADL Registry stores the metadata (information) about the digital object, rather than the digital object itself. The ADL Registry accepts metadata for all types of digital objects such as elearning, computer-based training, pedagogies, technical reports, intelligent agents, and many other forms of performance enhancing content. Digital objects that are proposed, under development, completed, or being revised can be contributed to the ADL Registry in accordance with DODI 1322.20. Digital objects may either be SCORM or non-SCORM conformant. DoD Instruction 1322.26 specifies using the current version for newly acquired digital objects. Most organizations are either adhering to SCORM 2004 or SCORM 1.2. The specific SCORM version should be identified in the ADL Registry Learning Object Metadata (LOM) Technical Format element of the digital object metadata.

Digital Object Formats

Any format of digital object may be contributed to the ADL Registry, as long as its metadata adheres to the ADL Registry Learning Object Metadata (LOM) schema and cardinality documents. One example of a digital object is a Sharable Content Object Reference Model (SCORM)-conformant content package. A SCORM package is a zip file containing information and organization of objects, and all related files needed to render the content. Such packages are self-describing through the use of an internal manifest and may include one simple object, or a collection of objects and supporting files. You may include content assets in the relation metadata element and include them in the SCORM conformant content package. By DoD policy, repositories must be able to store digital objects (in some format) and export them as SCORM content packages, but any other digital object types and formats may be registered at the discretion of the Repository Manager.

Transaction Types

There are seven types of transactions when contributing metadata to the ADL Registry. The transaction type is identified in the metadata.

• Insert. This is the most common transaction which adds a new, unique instance of metadata to the ADL Registry. Each metadata instance is assigned a unique ID. View an ADL Registry Submission Envelope (REG-T) INSERT Transaction Example.
• Update. This transaction updates an existing instance of registered metadata. The update action replaces the entire existing instance of metadata with the new metadata provided in the registry transaction. View an ADL Registry Submission Envelope (REG-T) UPDATE Transaction Example.
• Delete. This transaction deletes an existing instance of registered metadata. The delete action completely removes the identified metadata instance from the ADL Registry. As a consequence of the delete action, the metadata will not appear in search results (the digital object will no longer be able to be found through the ADL Registry). View an ADL Registry Submission Envelope (REG-T) DELETE Transaction Example.
• Deactivate. This transaction disables searches based on an existing instance (according to the metadata instance unique ID) of registered metadata until further notice. This action prevents the metadata instance from appearing in search results (the digital object will not be able to be found through the ADL Registry). The deactivate action does not delete any registered metadata instances. Thus, a metadata instance which was under review for any reason could be temporarily hidden and then later revealed again instead of being deleted and later re-inserted.
• Activate. This transaction enables a previously deactivated instance of registered metadata describing a digital object. This action indicates to the ADL Registry to include the metadata instance in relevant search results. The activate action only affects the identified metadata instance (based on the metadata instance unique ID) for a given content object.
• Move. This transaction informs the ADL Registry that the location of a registered digital object has changed.
• Withdraw. This transaction removes a registered digital object and all registered instances of metadata describing that object from the ADL Registry. Performing this action makes discovery (search) of the digital object, through the ADL Registry, no longer available.

Methods for Contributing Metadata

There are two methods for contributing metadata to the ADL Registry. For organizations familiar with creating XML transaction files, contributors may upload the XML files to the Registry; for organizations who prefer to enter the metadata in a web form, contributors may use the ADL Registry online form. Regardless of the method chosen, registration of the repository and contributors is required prior to contributing metadata.

Contributing Metadata using Online Form

Click to Contribute Metadata using the Online Form. Following successful submission of metadata, the contributor will receive one of two responses:

• If the file is small enough to process immediately, the Transaction ID will display.
• If the file is too large to process immediately (over 10mb), the Validation ID will display. The Transaction ID will be assigned when processed, and sent to the contributor via email.

The Validation and Transaction identifiers are used to view the status of a contribution.

Contributing Metadata using XML File

Click to Contribute Metadata using an XML File. Following successful submission of metadata, the contributor will receive one of two responses:

• If the file is small enough to process immediately, the Transaction ID will display.
• If the file is too large to process immediately (over 10mb), the Validation ID will display. The Transaction ID will be assigned when processed, and sent to the contributor via email.

The Validation and Transaction identifiers are used to view the status of a contribution.

View Contribution Status (back to top)

Click to View Contribution Status. In order to view the status of a contribution, you must have either a Validation or Transaction ID.

The Registry assigns and returns a Validation ID for every metadata submission, which can then be used to request the Validation Status of the submission. The Validation Status data will contain information regarding the processing status of the batch, including how many transactions have been validated, how many transactions remain, how many transactions had errors, etc. When all of the transactions in the batch have been validated, the Validation Status will contain a Transaction ID that can be used to get the status of the metadata submission. The Transaction Status data will contain Content Object identifiers and the assigned Metadata Instance identifiers if successful, and error messages if not.

If you receive an error message, or if your transaction has been rejected, contact the Helpdesk at 1.888.DOD-ADLR (1.888.363.2357) or adlrhelpdesk@adlnet.gov for further information.

Accessing the Practice ADL Registry (back to top)

Click to Access the Practice ADL Registry.

The data in the Practice Registry is not guaranteed for persistence, accuracy, or authenticity. The Practice ADL Registry is provided for organizations to practice registering, contributing, and searching digital objects using a common set of metadata. The Practice ADL Registry is identical to the ADL Registry in all respects except for access procedures and policies. It is important to note that as a sandbox, or test bed, the data in the Practice ADL Registry may periodically be deleted, and many of the records may not enable the 'get object' function for accessing the object itself. There is currently no mechanism for migrating data from the Practice ADL Registry to the ADL Registry.