Education Network of Australia

Education Network Australia (EdNA)

Dublin Core Element Label	Dublin Core Subelement Label	Scheme	Description
Contributor	*	**	A person or organization not specified in a Creator element but who has contributed to the resource content. 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.
Coverage	*	[Controlled Vocabulary / ISO 8601]**	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. 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. 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. 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. 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).
Creator	*	**	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. 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. 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.
Date	*	[ISO 8601]**	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. 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.
Description	*	**	A textual description of the content of the resource, including abstracts in the case of document-like objects or content descriptions in the case of visual resources. 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. 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.
Format	*	[MIME; AAT]**	The data format of the resource, used to identify the software and possibly hardware that might be needed to display or operate the resource. 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 & Architecture Thesaurus Browser: http://www.ahip.getty.edu/aat_browser/titles.html.
Identifier	*	[URL, URN]**	A string or number used to uniquely identify the resource. Examples for networked resources include URLs and URNs (when implemented). 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.
Language	*	[RFC 1766; ABS1267]**	The language of the intellectual content of the resource. 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. 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 EdNA is currently exploring automatic mapping between these different coding systems and the option of having both in EdNA generated metadata.
Publisher	*	**	The entity responsible for making the resource available in its present form, such as a publishing house, a university department, or a corporate entity. 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.
Relation	*	[Controlled vocabulary]** Note: Controlled term concatenated to text; e.g., “IsBasedOn Roderick West’s ...”	An identifier of a second resource and its relationship to the present resource. NOTES: This element permits links between related resources and resource descriptions to be indicated.
Rights	*	[URL]**	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. 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. No assumptions should be made by users if the Rights element is empty or not present.
Source	*	**	Objects, either print or electronic, from which this object is derived. 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.
Subject	*	[SCIS Subject Headings; OZJAC Subject Thesaurus; Asian and Pacific Skills Development Programme Thesaurus; Library of Congress Subject Headings]**	The topic of the resource. Typically, subject will be expressed as keywords or phrases that describe the subject or content of the resource. 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. Several existing systems are being considered as schemes and will be included in future versions of the EdNA Metadata Standard. These are: 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. 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. LCSH - Library of Congress Subject Headings. This thesaurus is being considered for use by the Higher Education sector.
Title	*	**	The name given to the resource, usually by the Creator or Publisher.. 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. The Title element in EdNA is limited to 80 characters. Longer entries will be truncated when displayed in EdNA. 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.
Type	*	[Default list: DC.Type Vocabulary]**	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. 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.

*EdNA does not use subelement qualifiers.
**Schemes required or suggested but not encoded.

EdNA Element Label EdNA Subelement
Label Scheme Description

Entered * ** Email of person or organisation approving the item for inclusion in EdNA.

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.

Approver * ** Email of person or organisation approving the item for inclusion in EdNA.

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.

Reassessment * ** The recommended date when the resource should be reassessed.

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.

Userlevel * ** Typical level of user for which the content would be most appropriate.

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

Categories * ** Categories in the EdNA Directory.

NOTES: This element should contain numbers representing categories in the EdNA Directory.

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.

Conditions * ** Do conditions apply to access to the resource?

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”.

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.

Indexing * ** To what extent should the EdNA software resource indexer follow links from this page?

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

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.

Review * ** A third party review of the resource.

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.

Version * ** 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.

*EdNA does not use subelement qualifiers.
**Schemes required or suggested but not encoded.

EdNA Element Label	EdNA Subelement Label	Scheme	Description
Entered	*	**	Email of person or organisation approving the item for inclusion in EdNA. 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.
Approver	*	**	Email of person or organisation approving the item for inclusion in EdNA. 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.
Reassessment	*	**	The recommended date when the resource should be reassessed. 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.
Userlevel	*	**	Typical level of user for which the content would be most appropriate. Notes: This element, when used, should always contain values from the EdNA recommended list of values.
Categories	*	**	Categories in the EdNA Directory. NOTES: This element should contain numbers representing categories in the EdNA Directory. 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.
Conditions	*	**	Do conditions apply to access to the resource? 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”. 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.
Indexing	*	**	To what extent should the EdNA software resource indexer follow links from this page? NOTES: The CONTENT value is a single string which may contain any one or two of these variables: depth, servers, and domains. 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.
Review	*	**	A third party review of the resource. 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.
Version	*	**	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.