innovation in metadata design, implementation & best practices

DCMI Education Community

Education Network Australia (EdNA)

<tr>

    <!-- Row 1 Column 1 -->

    <td bgcolor="#ff0000" width="15">

        <p align="center">

        <b><font size="-1">Dublin Core<br>

        Element Label</font></b>

        </p>

    </td>

    <!-- Row 1 Column 2 -->

    <td bgcolor="#ff0000" width="15">

        <p align="center">

        <b><font size="2">Dublin Core<br>

Subelement Label

        </p>

    </td>

    <!-- Row 1 Column 3 -->

    <td bgcolor="#ff0000" width="20" align="center">

        <b><font size="2">Scheme</font></b>

    </td>

    <!-- Row 1 Column 4 -->

    <td bgcolor="#ff0000" width="55" align="center">

        <b><font size="2">Description</font></b>

    </td>

</tr>

<tr>

    <!-- Row 2 Column 1 -->

    <td width="109" valign="top">

        <font size="2"><b>Contributor</b></font>

    </td>

    <!-- Row 2 Column 2 -->

    <td width="102" valign="top">

         *

    </td>

    <!-- Row 2 Column 3 -->

    <td width="134" valign="top">

        **

    </td>

    <!-- Row 2 Column 4 -->

    <td width="461" valign="top">

        <font size="-1">A person or organization not specified in a Creator element but who has contributed to

        the resource content.

        <p>NOTES: A person or organization not specified in a Creator element who has made significant

        intellectual contributions to the resource but whose contribution is secondary to any person

        or organization specified in a Creator element (for example, editor, transcriber, and

        illustrator). Where there is a co-author, this person should be included as a repeatable

        DC.Creator element. The preferred separator between family name and given name is a

        comma.<br>
      </p>

    </font>

</tr>

<tr>

    <!-- Row 3 Column 1 -->

    <td width="109" valign="top">

        <font size="2"><b>Coverage</b></font>

    </td>

    <!-- Row 3 Column 2 -->

    <td width="102" valign="top">

         *

    </td>

    <!-- Row 3 Column 3 -->

    <td width="134" valign="top">

        <font size="2">

        [Controlled Vocabulary /

        ISO 8601]**</font>

    </td>

    <!-- Row 3 Column 4 -->

    <td width="461" valign="top">

        <font size="-1">The spatial or temporal characteristics of the intellectual content of the resource. Spatial

        coverage refers to a physical region (e.g., celestial sector); use coordinates (e.g., longitude

        and latitude) or place names that are from a controlled list or are fully spelled out. Temporal

        coverage refers to what the resource is about rather than when it was created or made

        available (the latter belonging in the Date element); use the same date/time format (often a

        range) as recommended for the Date element or time periods that are from a controlled list

        or are fully spelled out.<p>NOTES ( Spatial Coverage): Content should be taken from the list of EdNA recommended values. Note that the values

        contain both the full State /Territory name and an abbreviation so that a search on either will

        be successful.<br>

        <br>

 The element is intended to be used mainly where information is only relevant in a particular

        jurisdiction. For example school or VET provider registration guidelines may only be

        applicable in a particular state. It may also be used to describe the physical location of an

        organisation. <br>

        <br>

 For many resources the state or territory in which it is produced will be of little relevance to

        its usefulness. Also, many resources in EdNA may not have this element and its use in

        searches should therefore be used sparingly to avoid unnecessary exclusion of resources. </p>

        <p>NOTES (Time Coverage): Content should be in the ISO 8601 format for date ranges. Time coverage will be most

        relevant for events (e.g., conferences, open days). It might also be used to give start and

        finish dates for particular course offerings. It should not be used for item management

        information (e.g., when an item is due for review or removal, as distinct from the date on

      which the event described has concluded). </p>

    </p></font>

</tr>

<tr>

    <!-- Row 4 Column 1 -->

    <td width="109" valign="top">

        <b>

        <font size="-1">Creator</font></b>

    </td>

    <!-- Row 4 Column 2 -->

    <td width="102" valign="top">

        <font size="-1">*

    <!-- Row 4 Column 3 -->

    <td width="134" valign="top">

       <font size="-1"> **</font>

    </td>

    <!-- Row 4 Column 4 -->

    <td width="461" valign="top">

        <font size="-1">The person or organization primarily responsible for creating the intellectual content of the

        resource. For example, authors in the case of written documents, artists, photographers, or

        illustrators in the case of visual resources.

        <p>NOTES: An entry containing an email address is highly desirable. Additional information can be

        included by repeating the element. For resources where users are likely to be searching by

        Author (e.g., articles and research reports), an element value with the full name is desirable.<br>

        <br>

 Personal names should be listed surname or family name first, followed by forename or given

        name. The preferred separator is a comma. When in doubt, give the name as it appears, and

      do not invert. </p>

    </p></font>

</tr>

<tr>

    <td width="109" valign="top">

        <b>

        <font size="-1">Date</font></b>

    </td>

    <td width="102" valign="top">

         *

    </td>

    <td width="134" valign="top">

        <font size="-1">[ISO 8601]**

    <td width="461" valign="top">

        <font size="-1">A date associated with the creation or availability of the resource. Such a date is not to be

        confused with one belonging in the Coverage element, which is associated with the resource

        only insofar as the intellectual content is somehow about that date.<br>

        <br>

        NOTES: As with any Dublin Core element, free text is an option, however it is highly desirable to

        have a precisely formatted scheme so that dates can be searched and processed, which is

        impractical with free text. Recommended best practice is defined in a profile of ISO 8601

        that includes (among others) dates of the forms YYYY and YYYY-MM-DD. In the case

        where the exact date is not known then just the year and month, or just the year is

        acceptable.<br>

</tr>

<tr>

    <td width="109" valign="top">

        <b>

        <font size="-1">Description</font></b>

    </td>

    <td width="102" valign="top">

         *

    </td>

    <td width="134" valign="top">

       <font size="-1"> **

    <td width="461" valign="top">

       <font size="-1"> A textual description of the content of the resource, including abstracts in the case of<br>

 document-like objects or content descriptions in the case of visual resources.<br>

        <br>

        NOTES: EdNA will only display the first 220 characters of a description in the EdNA Directory and

        EdNA search results. Up to 2000 characters can be entered and stored. The extra text is

        only displayed when a user requests additional information about an item (in Browse) by

        clicking on the "i" icon attached to the resource.<br>

        <br>

 The Description, in conjunction with the Title, should provide enough information for users

        to decide whether to access the document. Information in the description should be

        descriptive not promotional. It should be a pointer to the item rather than a summary of its

        contents. The description should give some information about the nature of the item.<br>

</tr>

<tr>

    <td width="109" valign="top">

        <b>

       <font size="-1"> Format</font></b>

    </td>

    <td width="102" valign="top">

         *

    </td>

    <td width="134" valign="top">

        <font size="-1">[MIME; AAT]**</font> </td>

    <td width="461" valign="top">

        <font size="-1">The data format of the resource, used to identify the software and possibly hardware that

        might be needed to display or operate the resource. <br>

        <br>

        NOTES: Formats, such as text/html, ASCII, Postscript file, executable application, or JPEG image

        may be included in this area. Assign a Format from Internet Media Types (MIME types). In

        principal, formats can include physical media such as books, serials, or other non-electronic

        media. A fully enumerated list of physical types recommended (but not endorsed) are found

        at the Art &amp; Architecture Thesaurus Browser:<br>

        <a href="http://www.ahip.getty.edu/aat_browser/titles.html">http://www.ahip.getty.edu/aat_browser/titles.html</a>.</font><br>

    </td>

</tr>

<tr>

    <td width="109" valign="top">

        <b>

       <font size="-1"> Identifier</font></b>

    </td>

    <td width="102" valign="top">

        <font size="-1">*</font>

    </td>

    <td width="134" valign="top">

        <font size="-1">[URL, URN]**</font>

    </td>

    <td width="461" valign="top">

        <font size="-1">A string or number used to uniquely identify the resource. Examples for networked resources include URLs and URNs (when implemented).<br>

        <br>

        NOTES: For EdNA usage a URL is the required format. The URL is already known if information is automatically harvested from pages on a Web site of an authorised organisation. This element may be used when information is collected by EdNA from authorised sites about resources available elsewhere on the Internet. <p>

</tr>

<tr>

    <td width="109" valign="top">

        <b>

        <font size="-1">Language</font></b>

    </td>

    <td width="102" valign="top">

        <font size="-1">*</font>

    </td>

    <td width="134" valign="top">

        <font size="-1">[RFC 1766; ABS1267]**</font>

    </td>

    <td width="461" valign="top">

        <font size="-1">The language of the intellectual content of the resource.<br>

        <br>

        NOTES: Dublin Core recommends that the content of this element should coincide with RFC 1766;

        examples include en, de, es, fi, fr, ja, th, and zh.<br>

        <br>

 The Australian Bureau of Statistic standard ABS1267 for languages is used by both AVETMISS and DEETYA. It has good coverage of Aboriginal languages. On this basis it has been recommended for inclusion by the schools metadata group but is not implemented in Version 1.0<br>

        <br>

 EdNA is currently exploring automatic mapping between these different coding systems and the option of having both in EdNA generated metadata. <br>

</tr>

<tr>

    <td width="109" valign="top">

        <b>

        <font size="-1">Publisher</font></b>

    </td>

    <td width="102" valign="top">

         <font size="-1">*

    <td width="134" valign="top">

       <font size="-1"> **

    <td width="461" valign="top">

        <font size="-1">The entity responsible for making the resource available in its present form, such as a

 publishing house, a university department, or a corporate entity.</font><br>

        <br>

        <font size="-1">NOTES: An entry containing an email address is highly desirable so that owners of documents listed in

        the EdNA Directory can be contacted efficiently. Additional information can be included by

        repeating the element.</font><br>

    </td>

</tr>

<tr>

    <td width="109" valign="top">

        <b>

        <font size="-1">Relation</font></b>

    </td>

    <td width="102" valign="top">

         <font size="-1">*</font>       

    </td>

    <td width="134" valign="top">

        <font size="-1">[Controlled vocabulary]**<br>

        Note: Controlled term concatenated to text; e.g., “IsBasedOn

        Roderick West’s ...”<br>

        </font>

    </td>

    <td width="461" valign="top">

        <font size="-1">An identifier of a second resource and its relationship to the present resource. <br>

        <br>

        NOTES: This element permits links between related resources and resource descriptions to be

        indicated.<br>

</tr>

<tr>

    <td width="109" valign="top">

        <b>

        <font size="-1">Rights</font></b>

    </td>

    <td width="102" valign="top">

         <font size="-1">*

    <td width="134" valign="top">

       <font size="-1"> [URL]**</font>

    </td>

    <td width="461" valign="top">

        <font size="-1">A rights management statement, an identifier that links to a rights management statement, or

        an identifier that links to a service providing information about rights management for the

        resource.</font><br>

        <br>

        <font size="-1">NOTES: In the initial implementation of EdNA metadata, this will be either a free text statement (e.g.,

        “free to Australian educational organisation”) or a URL pointing to the owner’s own

        copyright statement. <br>

        <br>

 No assumptions should be made by users if the Rights element is empty or not present.<br></font>

    </td>

</tr>

<tr>

    <td width="109" valign="top">

        <b>

        <font size="-1">Source</font></b>

    </td>

    <td width="102" valign="top">

         <font size="-1">*</font>       

    </td>

    <td width="134" valign="top">

        <font size="-1">**</font>

    </td>

    <td width="461" valign="top">

       <font size="-1"> Objects, either print or electronic, from which this object is derived. <br>

        <br>

        NOTES: Information about a second resource from which the present resource is derived. While it is

        generally recommended that elements contain information about the present resource only,

        this element may contain a date, creator, format, identifier, or other metadata for the second

        resource when it is considered important for the discovery of the present resource:

        recommended best practice is to use the Relation element instead. For example, it is

        possible to use a Source date of 1603 in a description of a 1996 film adaptation of a

        Shakespeare play, but it is preferred instead to use Relation “IsBasedOn” with a reference to

        a separate resource whose description contains a Date of 1603. Source is not applicable if

        the present resource is in its original form. <br>

       </font>

    </td>

</tr>

<tr>

    <td width="109" valign="top">

        <b>

        <font size="-1">Subject</font></b>

    </td>

    <td width="102" valign="top">

         <font size="-1">*</font>

    </td>

    <td width="134" valign="top">

        <font size="-1">[SCIS Subject Headings; OZJAC Subject Thesaurus; Asian and Pacific Skills Development

 Programme Thesaurus; Library of Congress Subject Headings]**

    <td width="461" valign="top">

       <font size="-1"> The topic of the resource. Typically, subject will be expressed as keywords or phrases that

        describe the subject or content of the resource. <br>

        <br>

 NOTES: Currently, no controlled vocabulary schemes or thesauri are implemented on EdNA. However, the SCIS (Schools Catalogue Information Service) subject headings list will be implemented on EdNA by October 1998. The subject element can therefore contain any keywords chosen by the user. It is recommended to include crucial words or phrases which are not part of the title or description. Use of SCIS subject headings is encouraged for school resources.<br>

        <br>

 Several existing systems are being considered as schemes and will be included in future

        versions of the EdNA Metadata Standard. These are: <br>

        <br>

 OZJAC Subject Thesaurus - The OZJAC product maintained by the Curriculum

 Corporation includes a thesaurus of subject area. This covers areas of most relevance to

        vocational education and training and university courses. <br>

        <br>

 APSDEP - This Thesaurus was developed for the Asian and Pacific Skills Development

        Programme (APSDEP). The Thesaurus deals with the broad subject areas and terms related

        to socio-economic development, especially those of major concern, such as labour,

        employment, industrial relations, social security, wage, job condition, health, personnel

        management, and vocational training. It is of particular relevance to the vocational education

        and training sector in Australia because it is maintained by the National Centre for

        Vocational Education Research (NCVER) and is used to catalogue items in the national

        VOCED database. <br>

        <br>

 LCSH - Library of Congress Subject Headings. This thesaurus is being considered for use

        by the Higher Education sector.<br>

       </font>

    </td>

</tr>

<tr>

    <td width="109" valign="top">

        <b>

        <font size="-1">Title</font></b>

    </td>

    <td width="102" valign="top">

         <font size="-1">*</font>       

    </td>

    <td width="134" valign="top">

        <font size="-1">**</font>

    </td>

    <td width="461" valign="top">

        <font size="-1">The name given to the resource, usually by the Creator or Publisher.. <br>

        <br>

        NOTES: The Title and Description elements are displayed when an item is linked as an approved

        item in the EdNA Directory or retrieved as a result of an EdNA search.<br>

        <br>

 The Title element in EdNA is limited to 80 characters. Longer entries will be truncated

 when displayed in EdNA.<br>

        <br>

 An item can appear in a number of contexts, including as a result of EdNA searches

 (including searches of the EdNA directory available from other Web sites). In combination

        with the description, the title should give users enough information to decide whether to

        access your document. The title/description combination should therefore be as self

        explanatory as possible, and not assume the context in which it will be viewed.<br>

        </font>

    </td>

</tr>

<tr>

    <td width="109" valign="top">

        <b>

        <font size="-1">Type</font></b>

    </td>

    <td width="102" valign="top">

         <font size="-1">*</font>

    </td>

    <td width="134" valign="top">

        <font size="-1">[Default list: DC.Type Vocabulary]**</font>

    </td>

    <td width="461" valign="top">

        <font size="-1">The category of the resource, such as home page, novel, poem, working paper, technical

        report, essay, dictionary. For the sake of interoperability, Type should be selected from the

        list below.<br>

        <br>

        NOTES: This is the type of resource the item describes, not the format of the Web resource itself

        –the latter will be implicit for the url (http, ftp, news etc.) or explicit in the ‘Format’ element. If

        the resource has content of mixed types then the Type element should be repeated to

        include all instances.<br>

        </font>

    </td>

</tr>

*EdNA does not use subelement qualifiers.

**Schemes required or suggested but not encoded.

<tr>

    <!-- Row 1 Column 1 -->

    <td bgcolor="#ff0000" width="15">

        <b><font size="-1"></font></b><center>EdNA Element Label</center>

    </td>

    <!-- Row 1 Column 2 -->

    <td bgcolor="#ff0000" width="15">

        <b><font size="-1"></font></b><center>EdNA Subelement<br>

        Label</center>

    </td>

    <!-- Row 1 Column 3 -->

    <td bgcolor="#ff0000" width="20">

        <b><font size="-1"></font></b><center>Scheme</center>

    </td>

    <!-- Row 1 Column 4 -->

    <td bgcolor="#ff0000" width="55">

        <b></b><center><font size="2">Description</font></center>

    </td>

</tr>

<tr>

    <!-- Row 2 Column 1 -->

    <td valign="top">

        <font size="-1"><b>Entered</b></font>

    </td>

    <!-- Row 2 Column 2 -->

    <td valign="top">

        <font size="-1">*</font>

    </td>

    <!-- Row 2 Column 3 -->

    <td valign="top">

        <font size="2">**</font>

    </td>

    <!-- Row 2 Column 4 -->

    <td valign="top">

        <font size="-1">Email of person or organisation approving the item for inclusion in EdNA. <br>

        <br>

        NOTES: This may be the same as the publisher when organisations are nominating their

        own resources, but different when nominating external resources. Normally

        created by the EdNA software when users with management rights approve

        resources. May also be coded in documents submitted by authorised organisations.

    </font>

</tr>

<tr>

    <!-- Row 3 Column 1 -->

    <td width="107" valign="top">

        <font size="2"><b>Approver</b></font>

    </td>

    <!-- Row 3 Column 2 -->

    <td width="104" valign="top">

        <font size="-1">*</font>

    </td>

    <!-- Row 3 Column 3 -->

    <td width="133" valign="top">

        <font size="-1">**</font>

    </td>

    <!-- Row 3 Column 4 -->

    <td width="462" valign="top">

       <font size="-1"> Email of person or organisation approving the item for inclusion in EdNA. <br>

        <br>

 Notes: This may be the same as the publisher when organisations are nominating their

        own resources, but different when nominating external resources. Normally

        created by the EdNA software when users with management rights approve

        resources. May also be coded in documents submitted by authorised

        organisations.

    </font>

</tr>

<tr>

    <!-- Row 4 Column 1 -->

    <td width="107" valign="top">

        <b>

        <font size="-1">Reassessment</font></b>

    </td>

    <!-- Row 4 Column 2 -->

    <td width="104" valign="top">

        <font size="-1">*

    <!-- Row 4 Column 3 -->

    <td width="133" valign="top">

        <font size="-1">**</font>

    </td>

    <!-- Row 4 Column 4 -->

    <td width="462" valign="top">

        <font size="-1">The recommended date when the resource should be reassessed. <br>

        <br>

        NOTES: Created in EdNA software at the time the resource is approved - will not be

        encoded in documents. Entered by content approving organisation for resources

        not automatically entered by an authorised site.

</tr>

<tr>

    <td width="107" valign="top">

        <b>

        <font size="-1">Userlevel</font></b>

    </td>

    <td width="104" valign="top">

         <font size="-1">*

    <td width="133" valign="top">

        <font size="-1">**</font>

    </td>

    <td width="462" valign="top">

        <font size="-1">Typical level of user for which the content would be most appropriate. <br>

        <br>

 Notes: This element, when used, should always contain values from the EdNA recommended list of values.</font>

    </td>

</tr>

<tr>

    <td width="107" valign="top">

        <b>

        <font size="-1">Categories</font></b>

    </td>

    <td width="104" valign="top">

        <font size="-1">*</font>

    </td>

    <td width="133" valign="top">

        <font size="-1">**</font>

    </td>

    <td width="462" valign="top">

        <font size="-1">Categories in the EdNA Directory. </font><br>

        <br>

        <font size="-1">NOTES: This element should contain numbers representing categories in the EdNA Directory.</font><br>

        <br>

 <font size="-1"><font size="-1">This can be the proposed categories for items suggested by users. For authorised

        organisations able to enter material directly into the EdNA Directory, this data

        will be used to automatically allocated items to the appropriate part of the

        Directory. 

</tr>

<tr>

    <td width="107" valign="top">

        <b>

       <font size="-1"> Conditions</font></b>

    </td>

    <td width="104" valign="top">

        <font size="-1">*

    <td width="133" valign="top">

        <font size="-1">**</font>

    </td>

    <td width="462" valign="top">

        <font size="-1">Do conditions apply to access to the resource?<br>

        <br>

        NOTES: Contains just the text “restricted” if conditions apply to access to the resource

        (e.g., payment, agreement to terms, user login information), or “unrestricted”. <br>

        <br>

 This would, for example, allow teachers to exclude resources which are known to

        be not freely available when searching for material for their students. Absence of

        this element should not be taken to imply that the resource is freely available. 

    </font>

</tr>

<tr>

    <td width="107" valign="top">

        <b>

        <font size="-1">Indexing</font></b>

    </td>

    <td width="104" valign="top">

        <font size="-1">*</font>

    </td>

    <td width="133" valign="top">

        <font size="-1">**</font>

    </td>

    <td width="462" valign="top">

        <font size="-1">To what extent should the EdNA software resource indexer follow links from this

        page?<br>

        <br>

        NOTES: The CONTENT value is a single string which may contain any one or two of these variables: depth, servers, and domains.<br>


 <font size="-1">The EdNA indexer, as well as performing full text indexing of pages identified in

        the EdNA directory, can optionally follow links in these pages and create indexes

        of these additional pages. These additional pages are not displayed through

        Browse and only show in EdNA search results.

</tr>

<tr>

    <td width="107" valign="top">

        <b>

        <font size="-1">Review</font></b>

    </td>

    <td width="104" valign="top">

        <font size="-1">*

    <td width="133" valign="top">

        <font size="-1">**</font>

    </td>

    <td width="462" valign="top">

        <font size="-1">A third party review of the resource.</font><br>

        <br>

        <font size="-1">NOTES: This element functions like a book review. Thus, by its nature the review would

        never be stored within the document for which it is a review, however reviews could be created as separate Web pages, with the EdNA software storing the URL of the review(s) as part of the information about a resource. The system for

        storing linkages between items and reviews of them is still being developed.</font>

    </td>

</tr>

<tr>

    <td width="107" valign="top">

        <b>

        <font size="-1">Version</font></b>

    </td>

    <td width="104" valign="top">

        <font size="-1">*</font>

    </td>

    <td width="133" valign="top">

        <font size="-1">**

    <td width="462" valign="top">

       <font size="-1">The Australian Government Locator Service (AGLS) Standard is recognised as

 an important whole-of-government initiative and provision is made to store

        AGLS-compliant metadata in the EdNA database. AGLS, like EdNA, adopts

        the Dublin Core as its basis. It adds two extra elements: AGLS.Function and

        AGLS.Availability.

</tr>

*EdNA does not use subelement qualifiers.

**Schemes required or suggested but not encoded.