DC.Title | Title | DC.Creator | DC.Publisher | DC.Rights | DC.Subject | Keywords | DC.Description | Description | DC.Language | DC.Coverage | DC.Coverage.jurisdiction | DC.Coverage.spatial | DC.Date.created | DC.Date.modified | DC.Type.documentType | DC.Type.category | DC.Format | DC.Identifier | AGLS.Availability | AGLS.Audience | Admin.Creator | Admin.DateCreated | Admin.DateValidTo
| Name | DC.Title |
| What do I put in this field? | The name of the resource. |
| Is this field compulsory? | Yes |
| Can I include more than one item in this field? | No |
| Is there a scheme for this field? | No |
| How do I complete this field? | Use the title as it appears on the resource itself.
Titles should be in proper case. |
| Example | <meta name=”DC.Title” content =“Guide to Law on the Internet – NSW”> |
| Name | Title |
| What do I put in this field? | The same name as given to DC.Title. |
| Is this field compulsory? | No, but it is recommended to improve the search results from search engines like Alta Vista. |
| Can I include more than one item in this field? | No |
| Is there a scheme for this field? | No |
| How do I complete this field? | Use the same title as in DC. Title field. |
| Example: | <Title>Guide to the Law on the Internet – NSW</Title> |
| Name | DC.Creator |
| What do I put in this field? | The name of the person or organisation primarily responsible for the content of the resource or the service. |
| Is this field compulsory? | Yes |
| Can I include more than one item in this field? | Yes |
| Is there a scheme for this field? | No |
| How do I complete this field? | In many organisations (eg. government departments) the organisation is regarded as the author, not the person. Use the name of the organisation that created or authored the resource. Record the name of the organisation as it was at the time of publication. |
| | If an organisation name has a well known acronym, add the acronym in brackets at the end of the name eg. Anti-Discrimination Board of NSW (ADB).
For personal creators, use the format "Lastname, Firstname". |
| | The creator is not the name of a person or contractor who has merely converted a resource into an internet version. However, if the resource's content has been produced under contract, then it may be appropriate to enter the name of the contractor (personal or company). |
| | In some cases an organisation may exist as a part of a larger organisation, for example, a division of an organisation. The creator field is designed to assist customers to identify the area responsible for the creation of the resource, as opposed to the organisation that publishes the resource. For example a resource may be created by the Registry of Encumbered Vehicles, but be published by the Department of Fair Trading. |
| | You can enter more than one name for joint creators. Separate these with semicolons. |
| Example: | <meta name="DC.Creator" content="LawAccess NSW"> |
| Name | DC.Publisher |
| What do I put in this field? | The name of the organisation responsible for producing the resource, such as a government department or community legal centre. |
| Is this field compulsory? | Yes |
| Can I include more than one item in this field? | Yes, if more than one organisation is responsible for making the resource available. |
| Is there a scheme for this field? | No |
| How do I complete this field? | Generally this will be the name of the organisation that owns the website, not the organisation that owns the computer on which the website may reside. For example, the website owner will be the Tenants’ Union, even if the website is sitting on the computers of a private Internet Service Provider (ISP). |
| | This field is different to the "DC.Creator" field. For example, while the Community Relations Division, Attorney General’s Department may have created the resource, it is published on a website owned by the NSW Attorney General's Department. In this case, the Division is the creator and the Department is the publisher.
In some cases, the creator and publisher may be the same organisation. |
| | For older resources, use the name valid for the date the resource was published.
If the publisher name has a well known acronym, add the acronym in brackets at the end of the name eg. Redfern Legal Centre Publishing (RLCP). |
| | You can enter more than one name for joint publications. Separate these with semicolons. |
 | <meta name="DC.Publisher" content="LawAccess NSW"> |
| Name | DC.Rights |
| What do I put in this field? | A copyright statement or link to a copyright notice. |
| Is this field compulsory? | No |
| Can I include more than one item in this field? | No |
| Is there a scheme for this field? | No |
| How do I complete this field? | Enter the details of the copyright owner or a link to website’s copyright notice. |
| | Generally use only if there are special constraints regarding the right to use the resource. Do not make up rights statements. Rights information should always be listed on the resource itself as well. |
| Example: | <meta name="DC.Rights" content="http://info.lawaccess.nsw.gov.au/lawaccess/lawaccess.nsf/pages/copyright"> |
| Name | DC.Subject |
| What do I put in this field? | A broad topic heading to describe the area of law the resource belongs in eg. employment. |
| Is this field compulsory? | Yes |
| Can I include more than one item in this field? | Yes |
| Is there a scheme for this field? | Yes
LIAC |
| How do I complete this field? | Select one or more of the terms from the LIAC Subject Headings Scheme. Separate these with semicolons. |
| | Determine the subject from the resource content. |
| | The LIAC subject headings has been designed to describe plain language legal resources. The Keywords field and DC. Description can be used for entering words not included in the LIAC subject headings. |
| Example: | <meta name=”DC.Subject” scheme= “LIAC” content =“Divorce; Family Law – Children”> |
| Name | Keywords |
| What do I put in this field? | Terms that assist in describing the resource in addition to those used in DC.Subject eg. renting; unfair dismissal. |
| Is this field compulsory? | No, but it is recommended to improve search results from search engines like Alta Vista. |
| Can I include more than one item in this field? | Yes |
| Is there a scheme for this field? | No |
| How do I complete this field? | The terms used to complete the keywords field should be descriptive of the content of the resource. |
| | Try to limit the number of keywords to a maximum of six. |
| | Try not to use keywords that are too broad, as this will result in users retrieving irrelevant material. Avoid terms such as "law", "rights" etc as these can be associated with almost any legal resource. The effect of using terms like these will be that customers searching for information on 'tenancy law' for example, may return any resources that used the term 'law' in the keywords field, regardless of whether it relates to tenancy. |
| | Other keywords to avoid are “legal information” and “legal advice”. |
| Example: | <meta name="Keywords" content="Internet guide; Legal websites"> |
| Name | DC.Description |
| What do I put in this field? | A concise description of the content or purpose of the resource. |
| Is this field compulsory? | Yes |
| Can I include more than one item in this field? | No |
| Is there a scheme for this field? | No |
| How do I complete this field? | Generally the description should be one or two sentences - just enough to help a user decide whether to link to the resource. Use information from the abstract or summary of the resource if available. |
| | The description will often be displayed as part of the search results. In writing a description think of the target audience and what they might need to know about the resource. |
| Example: | <meta name="DC.Description" content="This Guide is designed to help you search for reliable, up-to-date legal information on the Internet. It identifies the main starting points, called portals to legal information. It also lists, under subject headings some of the main websites that provide legal information"> |
| Name | Description |
| What do I put in this field? | The same content as DC.Description. |
| Is this field compulsory? | No, but it is recommended to improve the search results from search engines like Alta Vista. |
| Can I include more than one item in this field? | No |
| Is there a scheme for this field? | No |
| How do I complete this field? | Use the description from the DC.Description field. |
| Example: | <meta name="Description" content="
This Guide is designed to help you search for reliable, up-to-date legal information on the Internet. It identifies the main starting points, called portals to legal information. It also lists, under subject headings some of the main websites that provide legal information"> |
| Name | DC.Language |
| What do I put in this field? | The language of the resource’s content. |
| Is this field compulsory? | Yes |
| Can I include more than one item in this field? | Yes, for example, if the resource has links to documents in a variety of different languages. |
| Is there a scheme for this field? | Yes
SCHEME: RFC3066 Tags for the identification of languages.
Click here for a list of commonly used languages. The full list of codes is available at http://lcweb.loc.gov/standards/iso639-2/englangn.html. |
| How do I complete this field? | Use the default "en" for English. |
| | If there is not a two letter language code under the scheme you can use the applicable three letter code. |
| | More than one language can be entered. For example, the metadata might be on a cover page that links to versions of a document in different languages. Use a semicolon between each entry. |
| Example: | <meta name="DC.Language" |
| Name | DC.Coverage.jurisdiction |
| What do I put in this field? | The geographic area based on legal jurisdiction of the resource. |
| Is this field compulsory? | Yes |
| Can I include more than one item in this field? | Yes, for example, if the resource is a report about legal issues in a variety of different States or both Commonwealth and NSW. Separate items with a semicolon. |
| Is there a scheme for this field? | Yes
SCHEME: AglsJuri
New South Wales nsw
Commonwealth au
Queensland qld
South Australia sa
Tasmania tas
Victoria vic
Western Australia wa
Australian Antarctic Territory aat
Australian Capital Territory act
Indian Ocean Territories iot
Norfolk Island ni
Northern Territory nt
This scheme is available at http://www.naa.gov.au/recordkeeping/gov_online/agls/schemes/AglsJuri1.0.html |
| How do I complete this field? | Select a single State or Territory for content that is legally relevant to a single State or Territory jurisdiction only. For example, a guide to drafting a will in Victoria should be noted as 'vic' to allow users to limit search results to jurisdictionally relevant material.
Use the identifier 'au' if the content is relevant in all Australian jurisdictions or relates exclusively to Commonwealth legal jurisdiction. This may include a report on National Competition Policy implementation in Australian States or a guide to making an application in the Family Court. |
| | In some cases, content may be relevant to multiple jurisdictions. For example, a collaborative law reform report. In this case, all jurisdictions covered by the report should be included. |
| | Be careful to ensure a resource is legally accurate for all states or territories selected. If the resource has not been validated against all jurisdictions, a single State or Territory identifier should be selected. |
| | Use “au” for resources of general interest eg. an article on discrimination. |
| Example: | <meta name="DC.Coverage.jurisdiction" scheme=” AglsJuri” content="au; nsw"> |
| Name | DC.Coverage.spatial |
| What do I put in this field? | The application of the resource to a geographic area within New South Wales. |
| Is this field compulsory? | No, unless the resource describes a service. It is also recommended if the resource is applicable to a specific region. |
| Can I include more than one item in this field? | Yes, for example, if the resource is a report about legal issues in a variety of different regions. |
| Is there a scheme for this field? | Yes
SCHEME: AGSC
All Regions
Central West
Far West
Hunter
Illawarra
Mid-North Coast
Murrumbidgee
Murray
Northern
North Western
Richmond Tweed
South Eastern
Sydney
Blacktown
Canterbury – Bankstown
Central Northern Sydney
Central Western Sydney
Eastern Suburbs
Gosford - Wyong
Fairfield Liverpool
Inner Sydney
Inner Western Sydney
Lower North Shore
Outer South Western Sydney
Outer Western Sydney
Northern Beaches
St George – Sutherland
This scheme is based on the Australian Bureau of Statistics NSW Statistical Divisions and Sydney Subdivisions in the Australian Standard Geographical Classification Scheme (AGSC). |
| How do I complete this field? | This field is primarily used to describe the location of services. |
| | Select a region where the resource has been prepared for the use by people in a particular region, or where the resource defines services available to people in a particular region (eg. a page containing the contact details of a community legal centre in a particular region). |
| | If the resource is not specific to a region, but relevant to all regions, 'all regions' should be selected. |
| Example: | <meta name="DC.Coverage.spatial" scheme=”AGCS” content="All regions"> |
| Name | DC.Date.created |
| What do I put in this field? | The date the resource was made available in its present form. |
| Is this field compulsory? | Yes, unless the date is unknown. |
| Can I include more than one item in this field? | No |
| Is there a scheme for this field? | Yes
SCHEME: ISO8601 |
| How do I complete this field? | ISO8601 defines the format for dates. This scheme uses the format: YYYY or YYYY-MM or YYYY-MM-DD) eg. 1944-02-19. |
| | Try to enter full dates, if known. If the full date is not known enter the part of the date that is known eg. YYYY. Leave the field blank if the date is unknown. |
| | Date.Created is important to indicate the currency of the resource. It should be the date when the content was created/published, not the date put on the web. |
| Example: | <meta name="DC.Date.created" scheme="IS08601" content="2003-05"> |
| Name | DC.Date.modified |
| What do I put in this field? | The date the content of the resource was last modified (not including modification of visual presentation or structural organisation). |
| Is this field compulsory? | Yes, unless the date is unknown. |
| Can I include more than one item in this field? | No |
| Is there a scheme for this field? | Yes
SCHEME: ISO8601 |
| How do I complete this field? | ISO8601 defines the format for dates. This scheme uses the format: YYYY or YYYY-MM or YYYY-MM-DD) eg. 1944-02-19. |
| | Try to enter full dates, if known. |
| | If the resource has not been modified Date.Modified = Date.Created. |
| | Date.Modified should reflect the currency of the content of the resource. If the content is updated Date.Modified must also be updated. It should not be updated for trivial changes to the presentation of the resource. |
| Example: | <meta name="DC.Date.modified" scheme="IS08601" content="2003-05"> |
| Name | DC.Type.documentType |
| What do I put in this field? | The nature of the resource. |
| Is this field compulsory? | Yes |
| Can I include more than one item in this field? | Yes, but most resources should be allocated a single category. |
| Is there a scheme for this field? | Yes
SCHEME: JSMSDocument |
| How do I complete this field? | These headings should be used to define the purpose of a document, and to reflect the type of audience and complexity implicit in particular document types.This elements maps to JSMSDocument. |
| | Select one of the options to define the resource. See the following table for a detailed explanation of the categories JSMSDocument scheme. |
| Example: | <meta name="DC.Type.documentType" scheme="JSMSDocument" content="Resource guide"> |
| Name | DC.Type.category |
| What do I put in this field? | Broad description of the category of the resource. |
| Is this field compulsory? | No, unless you are describing a service |
| Can I include more than one item in this field? | No |
| Is there a scheme for this field? | Yes
document
service
agency |
| How do I complete this field? | Include the DC.Type.category element when you are describing a service. |
| Example: | Describing the LawAccess NSW service:
<meta name=”DC.Type.category” content=”service” >
<meta name=” DC.Type.ServiceType” content =”legal advice; legal information”> |
| Name | DC.Format
|
| What do I put in this field?
| The format of the resource (eg. Word, pdf, HTML etc).
|
| Is this field compulsory?
| No, but recommended to indicate the format of the resource to the customer.
|
| Can I include more than one item in this field?
| No
|
| Is there a scheme for this field?
| Yes
SCHEME: Internet Media Type IMT
|
| How do I complete this field?
| Commonly used values: text/html, application/pdf, image/jpeg, image/gif.
|
| [ | In an HTML cover page for a non-HTML resource, give the format of the actual resource eg. application/pdf. |
| Example: | <meta name="DC.Format" scheme="IMT" content="text/html "> |
| Name | DC.Indentifier |
| What do I put in this field? | A unique identifier for the resource eg. the web address of the resource. |
| Is this field compulsory? | Yes |
| Can I include more than one item in this field? | No |
| Is there a scheme for this field? | Yes
URI (Uniform Resource Identifier) |
| How do I complete this field? | Generally use the resource’s web address or unique resource identifier (URL). |
| | For a non-HTML resource with a cover page, generally use the cover page URL. This is recommended so that users can find out more information about the resource before deciding whether to open/download it. |
| | If the resource is not a web resource, you can use the ISBN or ISSN number separated by a semicolon. |
| Example: | <meta name="DC.Identifier" scheme="URI"content="http://info.lawaccess.nsw.gov.au/lawaccess/lawaccess.nsf/pages/guide"> |
| Name | AGLS.Availability |
| What do I put in this field? | Information relating to the availability of a non web based document or contact details for a service description. |
| Is this field compulsory? | No |
| Can I include more than one item in this field? | Yes |
| Is there a scheme for this field? | No |
| How do I complete this field? | Enter details of how the material may be obtained eg. full publishing details, contact details, price or details of a library where the item is available. |
| | This field may be used to automatically generate availability data for non web resources if a content management system is used to generate webpages. |
| Example: | <meta name="AGLS.Availability" content="Contact LawAccess NSW on 1300 888 529 for free copies of the Guide"> |
| Name | AGLS.Audience |
| What do I put in this field? | Information relating to the audience for a resource. |
| Is this field compulsory? | No |
| Can I include more than one item in this field? | Yes |
| Is there a scheme for this field? | Yes
Agls-audience
Aboriginal and Torres Strait Islanders
all
business
carers
children
community groups
employees
employers
gay and lesbians
government
jobseekers
low income earners
men
migrants
parent
people with disabilities
primary industry
rural
seniors
students
teachers
tourists
women
youth |
| How do I complete this field? | Use this field if the resource is directed at a particular audience. If this field is left blank it is assumed the resource is directed to all audience groups. |
| Example: | <meta name=“AGLS.Audience” scheme=“Agls-audience” content=“all”> |
Administrative Metadata
Metadata also allows you to include information that will assist with the effective updating and administration of your website. For example, where information has an expiry date, such as an upcoming event, the Admin.DateValidTo field can be used to prompt you to remove the resource from the internet. This will ensure users only receive information that is current and will help to keep your website up to date and relevant. Use of these fields is optional.
| Name | Admin.Creator |
| What do I put in this field? | The name of the person and/or organisation entering the metadata. |
| Is this field compulsory? | No |
| Can I include more than one item in this field? | Yes |
| Is there a scheme for this field? | No |
| How do I complete this field? | Include the name of any person who was involved in entering the metadata for the resource. |
| Example: | |
| Name | Admin.Date.Created |
| What do I put in this field? | The date the metadata is created. |
| Is this field compulsory? | No |
| Can I include more than one item in this field? | Yes |
| Is there a scheme for this field? | Yes
SCHEME: ISO8601 |
| How do I complete this field? | Include the date the metadata was first created. |
| | ISO8601 defines the format for dates. This scheme uses the format: YYYY or YYYY-MM or YYYY-MM-DD) eg. 1944-02-19. |
| | Try to enter full dates, if known. |
| Example: | <meta name="Admin.DateCreated" scheme="IS08601" content="2003-05-15"> |
| Name | Admin.DateValidTo |
| What do I put in this field? | The date the information is valid to. |
| Is this field compulsory? | No |
| Can I include more than one item in this field? | No |
| Is there a scheme for this field? | Yes
SCHEME: ISO8601 |
| How do I complete this field? | Include the date the metadata is valid to, for example, if the resource has an expiry date (eg. an announcement) this date will assist in determining when the resource should be removed from the internet. |
| | ISO8601 defines the format for dates. This scheme uses the format: YYYY or YYYY-MM or YYYY-MM-DD) eg. 1944-02-19. |
| | Try to enter full dates, if known. |
| Example: | <meta name="Admin.DateValidTo" scheme="IS08601" content="2004-05-15"> |
|