Elements in LAWI DATA AP
General Issues
It provides best recommended practices on cataloguing, however its emphasis is more on metadata exchange of agricultural information within the LAWI DATA Network.
CELEX and other Unique IDs
See CELEX numbers.
Code list:Country names (official short names in English) in alphabetical order as given in ISO 3166-1 and the corresponding ISO 3166-1-alpha-2 code elements.
It includes the two-letter ISO country code. This list can be found in the ISO3166-1 in three formats:
Text
HTML
XML
ISO 3166-1 has become one of the worldÂ’s most well known and widely used standards for coding country names. Using a code of letters and/or numbers to represent a country name can help save time and energy, and reduce the rate of error.
The LAWI DATA AP Element Set
Element | Qualifier Element Refinement(s) |
Encoding Schemes/Controlled List |
(DC) title | (DCTERMS) alternative | – |
(DC) creator | (LAWI) creatorPersonal | – |
(LAWI) creatorCorporate | ||
(LAWI) creatorConference | ||
(DC) publisher | (LAWI) publisherName | – |
(LAWI) publisherPlace | ||
(DC) date | (DCTERMS) dateIssued | (DCTERMS) W3CDTF |
(DC) subject | (LAWI) subjectClassification | (DCTERMS) DDC (DCTERMS) LCC (DCTERMS) UDC |
(LAWI) subjectThesaurus | LEGAL THESAURUS (DCTERMS) LCSH |
|
(DC) description | (LAWI) descriptionNotes | – |
(DCTERMS) abstract | ||
(DC) identifier | (DCTERMS) URI (LAWI) ISBN (LAWI) RN (LAWI) JN (LAWI) PN (LAWI) IPC (LAWI) DOI |
|
(DC)type | – | (DCTERMS) DCMIType |
(DC) format | (DCTERMS) extent | – |
(DCTERMS) medium | (DCTERMS) IMT | |
(DC) language | – | (DCTERMS) ISO639-2 (LAWI) ISO639-1 |
(DC) relation | (DCTERMS) is Version Of (DCTERMS) has Version (DCTERMS) is Replaced By (DCTERMS) replaces (DCTERMS) is Required By (DCTERMS) requires (DCTERMS) is Part Of (DCTERMS) has Part (DCTERMS) is Referenced By (DCTERMS) references (DCTERMS) is Format Of (DCTERMS) has Format (LAWI) is Translation Of (LAWI) has Translation |
(DCTERMS) URI (LAWI) ISBN (LAWI) RN (LAWI) JN (LAWI) PN (LAWI) IPC (LAWI) DOI |
(AGLS) availability | (LAWI) availabilityLocation | – |
(LAWI) availabilityNumber | ||
(DC) source | – | – |
(DC) Rights | (LAWI) rightsStatement (LAWI) TermsOfUse |
– |
(DC) Coverage | (DCTERMS) spatial | (DCTERMS) POINT (DCTERMS) ISO3166 (DCTERMS) TGN (DCTERMS) Box |
(DCTERMS) temporal | (DCTERMS) Period (DCTERMS) W3CDTF |
|
Titles: Title, Alternative Title
Title
Enter the main title of the document. If possible indicate the language of each title. Add additional titles if necessary
Meaning
A name given to the resource.
Objetive
This field is used to indicate the name by which the resource is formally known.
Guidance for adjusting code of Title
Selecting the Title
Copy the title in full, including the sub-title and any other secondary information. Use the exact wordings of the title, but not necessarily its capitalization and punctuation. Correct obvious typographical errors. Capitalize only the initial letter of the first word of the title and of proper names (personal, corporate, geographic, etc.) appearing in it.
e.g.
Title in original | Title for input |
Solar Radiation Energy and its Utilization by Lucerne (Medicagosativa L.) | Solar radiation energy and its utilization by Lucerne (Medicagosativa L.) |
Language of the Title
Indicate the language of the title using the xml:lang attribute. The language should be selected from the ISO639-2.
ISO 639 is the International Standard for language codes. The purpose of ISO 639 is to establish internationally recognised codes (either 2, 3, or 4 letters long) for the representation of languages or language families.
Uses of ISO 639
These codes are widely used in many different disciplines, for example for bibliographic purposes, in the library community, as well as for computerized systems, and the representation of different language versions on websites.
Using a code rather than the name of a language has many benefits as some languages are referred to by different groups in different ways, and two unrelated languages may share the same or similar name.
ISO 639 is composed of six different parts
Part 1 (ISO 639-1:2002) provides a 2 letter code that has been designed to represent most of the major languages of the world.
Part 2 (ISO 639-2:1998) provides a 3 letter code, which gives more possible combinations, so ISO 639-2:1998 can cover more languages.
Part 3 (ISO 639-3:2007) provides a 3 letter code and aims to give as complete a listing of languages as possible, including living, extinct and ancient languages.
Part 4 (ISO 639-4:2010) gives the general principles of language coding and lays down guidelines for the use of ISO 639.
Part 5 (ISO 639-5:2008) provides a 3 letter code for language families and groups (living and extinct).
Part 6 (ISO 639-6:2009) provides a 4 letter code, useful when there is a potential need to cover the entire range of languages, language families and groups and language variants in a system.
Punctuation in the Title
Omit any punctuation marks at the end of the title, but retain terminal question marks “?” and exclamation marks “!”, terminal brackets “]” and parentheses “)”. Retain the full stop “.” if the last word of the title is an abbreviation.
Use a space before continuing the text after any punctuation marks, e.g. full stops, commas.
Sub-Titles and Other secondary elements
Use a full stop and a space to separate main title and sub title and other secondary elements.
Additional Titles
Provide any other titles that may be useful.
Title Enrichment
When titles are meaningless, incomplete, ambiguous, misleading, or too general, title enrichment is highly recommended. Words (enrichment) should be added which will correct the deficiencies and will reflect the content of the document. All additional words should be enclosed in square brackets and either placed at the end of the original title or be interpolated in the title where most suitable, but generally not before the third word in the title.
e.g.
Examples of Title enrichment |
On the state of man [world agricultural situation] |
Technology and manpower policies [agricultural manpower, Mexico] |
Effect of cultural practices [in vineyards] on soil moisture management |
Conclusions and recommendation of the first Argentine Congress on Wool [sheep production, wood marketing] |
Cost of animal feed [pigs, substitution of maize by cassava] |
Core literature in human nutrition [a review article] |
Forestry and forest products [an automated bibliography] |
Model of soil salinity effects on crop growth [irrigation, drainage] |
The predator-control scene as of 1995 [coyote populations and sheep losses] |
Biographical articles
Titles of biographical articles lacking the name of the profession of the biographer and his country should be enriched.
e.g.
Title in original | Title for input |
Albert Pilat (1903-1974) | Albert Pilat (1903-1974) [mycologist, Czechoslovakia, obituary] |
Paulo da Cunha Nobrega: posthumous homage | Paulo da Cunha Nobrega: posthumous homage [biologist, Brazil] |
Abbreviated names
Abbreviated names of states or provinces or acronyms should preferably be written out to make them meaningful for data retrieval. If some elements are repeated in the title, it is sufficient to introduce them in extended form just once. Chemical notations that could require characters not available in the LAWI DATA character set should be rewritte, avoid subscripts and superscripts.
e.g.
Title in original | Title for input |
Rabies occurrence in Tracotapa, Guer. | Rabies occurrence in Tracotapa, Guerrero [Mexico] |
Research activities at IRRI | Research activities at IRRI [International Rice Research Institute, Philippines] |
The effect of soil Ca level in four soil pH-Mg combinations on the Ca and Mg level in sweet corn | The effect of soil Ca level in four soil pH-Mg [hydrogen-ion concentration-magnesium] combinations on the Ca and Mg level in sweet corn |
Some hazards in the application of TCNB to horticultural crops | Some hazards in the application of TCNB [tecnazene, 1, 2, 4, 5-tetrachloro-3-nitrobenzene] to horticultural crops [potatoes, peas, squash] |
Giberellin A3-3H | Giberellin A3-3H |
Alternative Title
Meaning
Translation of the title supplied by the user.
Objetive
This element is used to indicate translated titles not borne on the resource.
Guidance for adjusting code of Alternative Title
If the original title of the resource is translated by the user enter the information in this field. This filed must be supplemented with the language of the translation.
Creator: Personal and Entity
Personal Creator
Meaning
Person responsible for creating the intellectual content of the resource. There may be more than one.
Objetive
This field is used to enter the names of all the persons responsible for the intellectual content of a work and occasionally, the relationship of each creator to the work. It allows for locating resources based on the creator of those resources, for example, all resources by “Thien Kim”.
Enter in these fields the Creators associated with the resource. It may include a person, an organization, a service or an agency. This element describes all entities (Agents) that handle the resource i.e. creating or contributing.
Guidance for adjusting code of Personal Creator
Selecting the Personal Creator
All persons responsible for the intellectual content of a resource are treated as personal creators and their names should be entered in this field.
Order of Names
When multiple names appear on the resource, they should all be listed in the sequence shown on the resource. When there are principle creators and other creators who contributed to a resource, enter all the creators as they appear.
e.g.
Examples |
Brown, D. |
Holland, M. |
Coulter, J. |
Hindmarsh, P. |
Markin, J. |
Form of Name
In general, data in the personal creator field are entered in the following sequence:
surname, forename initial(s), prefixes, particles, role, affiliation.
For entry of creators in specific languages, see guidelines below.
Creator’s names usually consist of a first name (forename) and a surname (family name). The surname is entered first, followed by a comma and a space. Then the first name(s) or, in general, the initial(s) is (are) entered, each initial followed by a full stop without space,
e.g.
Examples |
Brown, A. |
Brown, A.F. |
Some names contain name fragments or particles like
e.g.
Example |
van, van der, vander, von, le, lo, la, da, de, del, de la, della, des, do, du, Jr, Sr, II, III. |
If these prefixes are transposed to the end of the name according to the rules below, they are separated from the preceding information by a space and are not followed by punctuation mark,
e.g.
Example |
Beethoven, L. van |
Special Languages
Transliteration is used for names from Arabic, Cyrillic and Greek alphabets. If the form of the creator’s name is already a transliteration, use it.
Portuguese terms denoting family relationships (e.g. Neto, Junior, Filho, and Sobrinho) form an integral part of the name, and are entered.
Example |
Coimbra Filho, A. F |
Compound Surnames
Compound Surnames, as in the case of Spanish surnames, may be written in full.
Pseudonyms/Former Names
Pseudonyms or former names may be entered in the Notes Field (Description/Notes).
Roles
For those creators who contributed to the intellectual content, if possible, specify their role in as shortest form possible. For editors and compilers, use ed. or comp. respectively. For all other roles, do not abbreviate.
Enter this information at the end of the name with any prefixes or particles and put the role in parentheses.
Examples |
Brown, A. (ed.) |
Smith, T. M. R. III (comp.) |
Mukuri, P. (Web Coordinator) |
Affiliations
Affiliations are defined as the name of the organization where the creators were employed or where they carried out their work, and should not be confused with the creatorÂ’s current addresses.
Affiliations are preferably entered in a standardized form according to rules for corporate creator, as shown in the following section on rules for entry of Corporate Creator.
Affiliations, if any, are separated from the creatorÂ’s name by a space and are enclosed between parentheses.
Affiliation Examples |
Coimbra Filho, A. F. (Instituto de Conservaçao da Natureza, Rio de Janeiro (Brazil). Div. de Pesquisas) |
Smith, T. M. R. III (comp.) (FAO, Rome (Italy)) |
Entity Creator
Meaning
Organization or agency responsible for creating the intellectual content of the resource.
Objetive
This field is used to enter the names of all the corporate bodies responsible for the intellectual content of a work and occasionally, the relationship of each corporate body to the work. It allows for locating resources based on the creator of those resources, for example, all resource from “Div. de Pesquisas”.
Guidance for adjusting code of Corporate Creator
Selecting Corporate Creator
Enter in this field the name and location of the corporate body identified on the resource as responsible for its content. The corporate body may be identified as:
- the body responsible for the intellectual content in the absence of a personal creator.
- the issuing body in conjunction with a personal creator.
- the assignee of a patent.
- the academic institution granting degrees.
- the country issuing legislative literature.
Form of name
Enclose the name of the country between parentheses and enter it as it appears in LEGAL THESAURUS.
If no place is given, add at least the country name between parentheses.
Example |
Asian Inst. of Journalism (Philippines) |
In general, when the corporate creator field consists of onlythe maininstitution, it is entered in the following sequence:
Name of institution, Place (Country)
Examples |
Instituto Nacional de Investigaciones Agrarias, Madrid (Spain) |
Forest Service, Berkley, Calif. (USA) |
Lembaga Oseanologi Nasional, Jakarta (Indonesia) |
Faculte des sciences agronomiques de lÂ’etat, Gembloux (Belgium) |
If it consists of subordinate bodies, it is entered in the following sequence:
Main Institution, Place of the subordinate body (Country).
Smallest subordinate body
Examples |
Instituto Nacional de Tecnologia Agropecuaria, Buenos Aires (Argentina). Inst. de. Patologia |
University of the West Indies, St. Augustine (Trinidad and Tobago). Dept. of Agricultural Extension |
Smallest subordinate bodies which are departments of universities should be written in the form “Dept. of …” and not “… Dept.”
Example |
University of the Philippines at Los Banos, College, Laguna (Philippines). Dept. of Soil Science |
City names which repeat as part of the name of the main element are, in general, omitted.
Example |
University of Kabul (Afghanistan) |
Enter the names of the city in its English form.
e.g.
Original | Correct Entry |
Muenchen | Munich |
Roma | Rome |
Moskva | Moscow |
Always indicate the location, place and country, at the end of the names of the corporate body or its main institution.
Enter the corporate creator in the language of the corporate body. In the case of an international organization where no country is easily identified, enter its official acronym instead of its location, preferring the English, French or Spanish form in this order of preference.
Capitalize all letters of the acronym. Do not leave spaces between the letters of an acronym and do not separate those letters with full stops.
Examples | |
ASEAN | Association of South-East Asian Nations |
BENELUX | Benelux Economic Union |
CAB | Commonwealth Agricultural Bureau |
CENTO | Central Treaty Organization |
ECA | Economic Commission for Africa |
ECAFE | Economic Commission for Asia and the Far East |
ECE | Economic Commission for Europe |
ECLAC | Economic Commission for Latin America and the Caribbean |
ECOSOC | Economic and Social Council |
ESCAP | Economic and Social Commission for Asia and the Pacific |
ESCWA | Economic and Social Commission for Western Asia |
FAO | Food and Law Organization of the United Nations |
GATT | General Agreement on Tariffs and Trade |
IAEA | International Atomic Energy Agency |
IBRD | International Bank for Reconstruction and Development |
ICAO | International Civil Aviation Organization |
ICJ | International Court of Justice |
ICSC | International Civil Service Commission |
IEA | International Energy Agency |
IFAD | International Fund for Agricultural Development |
ILO | International Labour Organization; International Labour Office |
IMF | International Monetary Fund |
IMO | Intergovernmental Maritime Organization |
IMO | International Maritime Organization |
ITU | International Telecommunication Union |
NATO | North Atlantic Treaty Organization |
OAS | Organization of American States |
OAU | Organization of African Unity |
OECD | Organization for Economic Co-operation and Development |
ONU | United Nations University |
UN | United Nations |
UNCTAD | United Nations Conference on Trade and Development |
UNDP | United Nations Development Programme |
UNDRO | Office of the United Nations Disaster Relief Co-ordinator |
UNEP | United Nations Environment Programme |
UNESCO | United Nations Educational, Scientific and Cultural Organization |
UNFPA | United Nations Fund for Population Activities |
UNHCR | Office of the United Nations High Commissioner for Refugees |
UNICER | United Nations Children’s Fund |
UNIDO | United Nations Industrial Development Organization |
UNITAR | United Nations Institute for Training and Research |
UNRISD | United Nations Research Institute for Social Development |
UNRWA | United Nations Relief and Works Agency for Palestine Refugees in the Near East |
WHO | World Health Organization |
Publisher: Publisher Name, Place of Publication
Publication types
?
The XML schema can be found here using this link: http://purl.org/info:eu-repo/schemas/xmls/2010/04/15/publicationTypes.xsd Publication type ontology: http://purl.org/info:eu-repo/ Usage for actionable reference to machine readable content: add http://purl.org/ as a prefix to the authoritative term e.g. http://purl.org/info:eu-repo/semantics/annotation |
Namespace | Type | Term | Description | Used by project | ||||
---|---|---|---|---|---|---|---|---|
info:eu-repo | / | semantics | / | article | article or an editorial published in a journal. (ed. Should this be specified specifically as an Scholarly article? Or does this list of publication types define a scholarly context by default?) | DRIVER SURF NEEO |
||
info:eu-repo | / | semantics | / | bachelorThesis | lowest level of a thesis (normally after three years of study). See also http://en.wikipedia.org/wiki/Diplom | DRIVER SURF |
||
info:eu-repo | / | semantics | / | masterThesis | intermediate level of a thesis (normally after four or five years of study). See also http://en.wikipedia.org/wiki/DiplomThis also refers to theses of the pre-Bologna period for degrees that are at the same level as what now is known as a master degree | DRIVER SURF |
||
info:eu-repo | / | semantics | / | doctoralThesis | highest level of a thesis normally after more than four or five years of study. See also http://en.wikipedia.org/wiki/DiplomAlso everything equal and higher then a Doctoral thesis, that does not follow the “Bologna Convention”, will be put in the category doctoralThesis. A free text field will Provide the opportunity to specify this further | DRIVER SURF |
||
info:eu-repo | / | semantics | / | book | book or monograph | DRIVER SURF |
||
info:eu-repo | / | semantics | / | bookPart | part or chapter of a book | DRIVER SURF |
||
info:eu-repo | / | semantics | / | review | review of a book or article | DRIVER | ||
info:eu-repo | / | semantics | / | conferenceObject | all kind of documents related to a conference, p.e. conference papers, conference reports, conference lecture, papers published in conference proceedings, conference contributions, reports of abstracts of conference papers and conference posters | DRIVER | ||
info:eu-repo | / | semantics | / | lecture | lecture or presentation presented during an academic event, e.g., inaugural lecture. Excluded is a conference lecture (see conferenceItem) | DRIVER SURF |
||
info:eu-repo | / | semantics | / | workingPaper | a preliminary scientific or technical paper that is published in a series of the institution where the research is done. Also known as research paper, research memorandum or discussion paper. The difference with a preprint is that a workingPaper is published in a institutional series. Examples are: working papers, research papers, research memoranda and discussion papers | DRIVER SURF |
||
info:eu-repo | / | semantics | / | preprint | like a workingPaper this is a preliminary scientific or technical paper, but it is not published in a institutional series. The paper is intended to be published in a scientific journal or as a chapter in a book | DRIVER SURF |
||
info:eu-repo | / | semantics | / | report | this is a more or less a rest category and covers commission reports, memoranda, external research reports, internal reports, statistical report, reports to funding agency, technical documentation, project deliverables etc. Excluded are conference reports (See conferenceItem) | DRIVER SURF |
||
info:eu-repo | / | semantics | / | annotation | note to a legal judgmen | DRIVER SURF |
||
info:eu-repo | / | semantics | / | contributionToPeriodical | contribution to a newspaper, weekly magazine or another non-academic periodical | DRIVER SURF |
||
info:eu-repo | / | semantics | / | patent | patent | DRIVER SURF |
||
info:eu-repo | / | semantics | / | other | especially meant for non-publication data like research data, audio-visual materials, animations etc. | DRIVER | ||
info:eu-repo | / | semantics | / | conferenceObject | All kinds of documents related to a conference, e.g., conference papers, conference reports, conference lecture, papers published in conference proceedings, conference proceedings, conference contributions, reports of abstracts of conference papers and conference posters | DRIVER | ||
info:eu-repo | / | semantics | / | reportPart | part of a report | SURF | ||
info:eu-repo | / | semantics | / | bookReview | book review | SURF | ||
info:eu-repo | / | semantics | / | conferencePaper | paper published in conference proceedings | SURF | ||
info:eu-repo | / | semantics | / | researchProposal | documentation for grant request | SURF | ||
info:eu-repo | / | semantics | / | studentThesis | this refers to theses of the pre-Bologna period for degrees that are at the same level as what now is known as a master degree | SURF | ||
info:eu-repo | / | semantics | / | technicalDocumentation | technical documentation | SURF | ||
info:eu-repo | / | semantics | / | conferencePaper | paper published in conference proceedings | NEEO | ||
info:eu-repo | / | semantics | / | conferencePoster | poster presented at a conference | NEEO | ||
info:eu-repo | / | semantics | / | conferenceProceedings | the conference proceedings | NEEO | ||
info:eu-repo | / | semantics | / | conferenceContribution | contribution to a conference but not published in a conference | NEEO | ||
info:eu-repo | / | semantics | / | conferencePaper | paper published in conference proceedings | DARE | ||
info:eu-repo | / | semantics | / | ConferenceItem | contribution to a conference but not published in a conference | UKOLN | ||
info:eu-repo | / | semantics | / | ConferencePaper | contribution to a conference but not published in a conference | UKOLN | ||
info:eu-repo | / | semantics | / | ConferencePoster | contribution to a conference but not published in a conference | UKOLN |
conferenceObject of Driver includes all other conference-related publications. This can be used if none of the more specific publicationtypes comply.
Within conferenceObject are two types: conferenceProceedings as proposed by NEOO and ConferenceItem from the vocabulary of UKOLN. The type conferenceProceedings is used for authors who want to include the conference proceedings of which they are the editor. It is helpful if conference proceedings are contained in the repositories as compound objects. ConferenceItem is not really necessary, because there are more specific types who cover all sorts of ConferenceItems: ConferencePaper and conferenceContribution. The distinction between these two subtypes is the whether or not it’s included in conference proceedings.
conferenceContribution has a subtype: conferencePoster. Not published readings for a conference are a conferenceObject, a ConferenceItem and a ConferenceContribution.
The class-subclass relations can be represented with the following hierarchy.
conferenceObject    conferenceProceedings    ConferenceItem       conferencePaper = ConferenceItem in conferenceProceedings       conferenceContribution = ConferenceItem not in conferenceProceedings          conferencePoster
The term conferenceContribution is confusing. A more clear term is concerenteItemNotInProceedings. The proposal is to adopt conferenceObject, conferenceProceedings, conferencePaper, conferenceItemNotInProceedings, conferenceContribution (owl:sameAs conferenceNotInProceedings; the latter is the preferred term) and conferencePoster in the info:eu-repo/semantics namespace. If we specify in a more formal way the semantic relations, we can use ConferenceItem from the UKOLN vocabulary.
The new situation can be visualised as follows:
The proposal is to use conferenceProceedings, conferencePaper and conferencePoster within SURFshare. conferenceItemNotInProceedings can be used as rest category.
Mappings with SWAP
Use for publication types identifiers from the info:eu-repo/semantics/ namespace, see the first column of the following table. E.g., the URI for articles is info:eurepo/semantics/article. The second column contains the vocabulary of the Eprints Application Profile (also known as Scholarly Works Application Profile – SWAP) (http://www.ukoln.ac.uk/repositories/digirep/index/Eprints_Type_Vocabulary_Encoding_Scheme). This vocabulary is included only for comparison reasons.
info:eu-repo/semantics/ | http://purl.org/eprint/type/ | Description |
annotation | note to a legal judgment | |
article | JournalArticle | article in a journal |
bachelorThesis | Thesis (broader) | bachelor thesis |
book | Book | book or monograph. |
bookPart | BookItem | part or chapter of a book |
bookReview | BookReview | book review |
conferencePaper | ConferencePaper | paper published in conference proceedings |
contributionToPeriodical | contribution to a newspaper, weekly magazine or another non-academic periodical | |
doctoralThesis | Thesis (broader) | PhD dissertation |
researchProposal | documentation for grant request | |
lecture | Published lecture presented during an academic event, e.g., inaugural lecture | |
masterThesis | Thesis (broader) | |
patent | Patent | patent |
preprint | Report (broader) | like a research paper this is a preliminary scientific or technical paper, but it is not published in a institutional series. The paper is intended to be published in a scientific journal or as a chapter in a book. |
report | Report (broader) | this is a more or less a rest category and covers commission reports, memoranda, conference reports, external research reports, internal reports, statistical report, reports to funding agency, etc. |
studentThesis | Thesis (broader) | this refers to theses of the pre-Bologna period for degrees that are at the same level as what now is known as a master degree |
technicalDocumentation | technical documentation | |
workingPaper | WorkingPaper | a preliminary scientific or technical paper that is published in a series of the institution where the research is done. Also known as research paper, research memorandum or discussion paper. The difference with a preprint is that a workingPaper is published in a institutional series. |
ScholarlyText | all the other types are a sub-classe of this type | |
ConferenceItem | covers conference papers and conference posters | |
ConferencePoster | poster presented at a conference | |
JournalItem | a contribution to a journal; includes articles, editorials, conference reports, etc. | |
NewsItem | news item | |
SubmittedJournalArticle | the author’s original manuscript submitted to and/or accepted by a journal. When not accepted it is a info:eu-repo/semantics/preprint or a info:eu-repo/semantics/workingPaper and when accepted it is a info:eu-repo/semantics/article |
Publisher Name
Meaning
A publisheris the individual, group, or organization named in the document as being responsible for that documentÂ’s publication, distribution, issuing, or release.
Objetive
This element provides the name of the individual, group, or organization which controls or publishes the item. It allows for identification of a resource.
Lack of Publisher
When there is no publisher, enter (np) or (s.n.) in parentheses.
Note: Do not substitute the name of the publisher with that of a printer when no publisher is given.
Date: Date of Publication
Date
Meaning
A date of an event in the lifecycle of the resource.
Objetive
It allows for discovery and distinction between resources.
Guidance for adjusting code of Publisher Date
Selecting the Date
Typically, Date will be associated with the creation or availability of the resource. Recommended best practice for encoding the date value in XML is defined in a profile of ISO 8601 [W3CDTF] and includes (among others) dates of the form YYYY-MM-DD
Date of Publication
Meaning
Date when the resource was made available to the public.
Objetive
It allows for discovery and distinction between resources.
Guidance for adjusting code of Publication Date
Selecting the Date
If the date of issue is different from stated date of publication, and if it is of great importance, e.g. for taxonomic publications, it can be repeated. If it is unclear, based on your judgement, place it in the Notes filed.
Subject: Classification and Thesaurus
Subject
Meaning
The topic of the content of the resource.
Objetive
This field is used to provide free-text keywords, which are not taken from a controlled vocabulary or classification scheme.
Enter in this field the subject information about the resource. It can be free-text, come from a controlled vocabulary or a classification scheme. However, it is recommended to use controlled vocabulary or lists.
Select values from ISO639-2 or the ISO639-1 list
Subject Classification
Meaning
A system of classifying information resources whereby main classes and sub-classes are designated by codes.
Objetive
The field is used to provide the subject category which describes the content of the resource. It allows for systematic arrangement and browsing of resources.
Subject schemes
The subject categories can be selected, preferably, from LAWI DATA Categorisation Scheme.
Classification Schemes
Namespace | Type | Term | Description | Used by project | ||||
---|---|---|---|---|---|---|---|---|
info:eu-repo | / | classification | / | ddc | Dewey Decimal Classification (DDC) http://www.oclc.org/dewey/ |
|||
info:eu-repo | / | classification | / | udc | Universal Decimal Classification http://www.udcc.org/http://www.udcc.org/ |
|||
info:eu-repo | / | classification | / | lcc | Library of Congress Classification http://www.loc.gov/catdir/cpso/lcco/http://www.loc.gov/catdir/cpso/lcco/ |
|||
info:eu-repo | / | classification | / | lcsh | Library of Congress Subject Headings (LCSH) | |||
info:eu-repo | / | classification | / | swd | Schlagwortnormdatei (SWD) | |||
info:eu-repo | / | classification | / | bicssc | Book Industry Communication – Standard Subject Categories http://www.bic.org.uk/7/BIC-Standard-Subject-Categories/ |
Open Access Publishing in European Networks (OAPEN) http://www.oapen.org/ |
||
info:eu-repo | / | classification | / | nbc | Nederlandse Basisclassificatie (Dutch Basic Classification) http://www.kb.nl/vak/basis/bc04.pdf |
HBO-Kennisbank http://www.hbo-kennisbank.nl |
Other possible classifications schemes are:
Name | Label | URI |
LAWI DATA Subject Categories | ||
CABI Codes | CABC | http://www.cabi-publishing.org/ |
Dewey Decimal Classification | DDC | http://www.oclc.org/dewey/index.htm |
Library of Congress Classification | LCC | http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html |
Universal Decimal Classification | UDC | http://www.udcc.org/ |
Subject Thesaurus
Meaning
A classified list of terms or keywords for use in indexing and information retrieval.
Objetive
The field is used to provide keywords which describe the content of the resource. It allows for consistent access to information resources regardless of the language of the resource.
Guidance for adjusting code of subject Thesaurus
This field is used to provide descriptors from a controlled vocabulary.
Indexing resources
LAWI DATA Guidelines for indexing are available at:
However, each user can use its own guidelines.
Possible Thesauri
The LAWI DATA AP recommends the following choices of schemes.
Name | Label | URI |
LEGAL THESAURUS | LEGAL THESAURUS | |
CABI Thesaurus | CABT | http://www.cabi-publishing.org/ |
Library of Congress Subject Headings | LCSH | http://lcweb.loc.gov/cds/lcsh.html#lcsh20 |
Other schemes, not listed above can also be used.
Description: Notes, Edition, Abstract
Description Notes
Meaning
A brief statement, annotation, comment, or elucidation concerning any aspect of the resource. Information in a general note is information about the item that the user has deemed important to add to the record.
Guidance for adjusting code of Notes
Enter as a note any information deemed necessary for the identification of the item. Certain notes may be entered in prescribed ways (see below). If a specific note is not mentioned, use ownÂ’s judgment in formulating the note.
Standard Notes
Some notes are expressed in standard format to allow searching of this field by computer. Other notes may be entered in any preferred style but they should be concise. Repeat the note field for each note. The most frequent annotation of notes is listed in the following table.
English |
also issued as |
also issued in |
Author variant |
bibliography |
dictionary |
glossary, glossaries |
ref. |
Summary only/Summaries only (see below) |
Summary/Summaries (see below) |
translation |
ill., fig. |
translation |
map, maps |
Special Notes
Summaries (Item Has a Summary)
Enter summary statements into this field in the form:
– the word Summary or Summaries (or its equivalent in any other language) and the code(s) of the respective language(s) between parentheses. Use the List of language codes given in ISO639-2 [8]. If there is no appropriate language code is available enter the name of the language in full.
Examples |
Summaries (Es) |
Resumé (Fr, Fi, Da) |
– Include the language of the summary even if it is in the same language as the item.
Summaries (Item Is a Summary)
If the text consists only of a summary, an abstract, a short communication, a corresponding statement should be entered in this field in the form Summary only or Summaries only or their equivalent in any other language. In this case, the language of the summary should be in the language element, e.g. item is a summary in English
Examples | |
Item is in English and the note is in French. | Note: Resumés seulement Language: Fr |
Item is in Vietnamese and the note is in French. | Note: Resumés seulement Language: Vi |
Do not confuse Summary notes with Abstracts.
Description Abstract
Meaning
An abstract is a summary of a document designed to give the user a clearer idea about the entryÂ’s contents. It should be intelligible in itself, without reference to the entry, but it is not intended to substitute for the resource itself.
Objetive
An abstract should be a non-critical, informative digest of the significant contents and conclusions of the resource. A well-prepared abstract helps readers to decide whether a publication covers subjects that are of interest to them.
Guidance for adjusting code of Abstract
Enter in this field the abstract of the resource. An abstract is mandatory.
The abstract field must come with a language attribute which indicates the language or languages in which the abstract is. Enter the language code from the ISO639-2 language code.
Guidelines for Formulating the Abstract
An abstract should state the Objetive, methodology, results and conclusions presented in the original document. Unfamiliar terms, trade names, acronyms, abbreviations or symbols should be defined when used in an abstract.
Apply the following criteria in preparing abstracts:
- Do not begin the abstract by repeating the title.
- Abstracts are written as one single paragraph without columns, tables, or graphs.
- For practical Objetives, the maximum length of a single abstract should generally not exceed 400 words. An average length of 100 to 250 words is recommended. If longer abstracts are available within the original document they may be edited or compressed.
- Several versions in different languages may be provided in repeated abstract fields.
Identifier
Identifiers (Standard Numbers)
Meaning
Identifiers (Standard numbers) are numbers taken from the item with exceptions mentioned below. They can be ISSN, ISBN, Patent numbers and other numbers not assigned by the cataloguing agency.
Objetive
This field is used to enter numbers which can give unambiguous access to the document. There often will be two or more Identifiers and they should be all entered whenever available. Each Identifiermust be accompanied by the scheme it uses for value formatting. Some of the commonly used schemes may be:
Scheme | Applicability Conditions |
IPC | International Patent Classification |
ISBN | Book |
ISSN | International Standard Serial Number |
CELEX | CELEX identifier |
PN | Patent Number |
RN | Report Number |
URI | when a resources is electronically available. |
There can be many numbers assigned to a document. This field is reserved for standard numbers taken from the item. Some of the numbers may be input in authorized form. The UR is also placed in this field.
Numbers assigned by cataloguing institutions for internal Objetives such as Call Number are not entered here, but placed into the Availability element. (see Availability)
International Patent Classification (IPC)
The International Patent Classification is the code assigned to a patent or patent-like document by many national industrial property offices and is identified by
WIPO/INID Code 51(World Intellectual Property Organization (WIPO), Geneva (Switzerland). WIPO Handbook on Patent Information and Documentation. 4 vols. July 1982-October 1986).
For information about International Patent Classification (IPC) (e.g., IPC Guide, Nice Agreement, Locarno Agreement, etc.) please visit the International Classification Resources page.
Patent Number (PN)
See WIPO Guide to using patent information.
ISBN
The International Standard Book Number is recorded in this field as a ten-digit code. The code is recorded as given on the unit, preferably retaining the hyphens.
Examples | |
ISBN | 0-571-0898-9 |
ISBN | 90-7000-234-5 |
Note: National standard book numbers are not entered.
ISSN
The International Standard Serial Number is recorded in this field as an eight-digit code (retain the hyphen).
Example | |
ISSN | 0029-0254 |
CELEX
CELEX is the documentation system for EU documents produced by the Office for Official Publications of the European Communities (EUR-OP). CELEX numbers are the unique reference numbers assigned to EU documents on CELEX.
CELEX numbers are made up of the following component parts:
Sector (1 number) + Year (4 numbers)* + Document Type (1 or 2 letters) + Document Number (3-4 numbers)
For example, the CELEX number for Van Gend en Loos is 61962CJ0026, which breaks down as follows:
Element | Meaning | |
---|---|---|
6 | Sector | Case law |
1962 | Year | The CELEX Year of the document.* |
CJ | Document Type | Judgments of the Court of Justice. |
0026 | Document Number | The sequential number of the document within that Document Type and Year. |
NOTE: Judgments of the Court of Justice on a reference for a preliminary ruling will take as their CELEX Year the year in which the reference was received by the Court, which is unlikely to be the same as the year the eventual judgment was published.
So, we can see that 61962CJ0026 is the ECJÂ’s judgment in case number 26 from the year 1962.
Some other examples of CELEX numbers are:-
- 31993L0013 – Directive 93/13/EEC
- 11957E086 – Article 86 of the Treaty of Rome
- 91993E1112 – Written question 1112 from the year 1993
A full rundown of Sectors and Document Types can be found in this table. Note that each Sector has its own set of document types. Therefore, in order to parse a CELEX number using the table you must first locate the entry for the Sector and then find the Document Type in the types listed for that Sector.
Report Number
This number is an alphanumeric identification assigned to a report by the organization which issued it.
Enter in this field any report numbers given on the resource. Report numbers may be standardized. If more than one report number is assigned, they may be entered in repeating Identifier fields.
Report Numbers in multiple parts
Occasionally a report is issued in several parts or in several editions. The relevant statement is then made in parentheses immediately after the report number using the following list of abbreviations,
e.g.
Examples |
TID–2236 (pt.1) |
TID–11295(ed.4) |
ORNL–3904(rev.) |
Term | Abbreviation |
Addendum | add. |
Amendment | amend. |
Appendix | app. |
Book | bk. |
Chapter | ch. |
Edition | ed. |
Number | no. |
Part | pt. |
Revised, Revision | rev. |
Section | sect. |
Series | ser. |
Summary | summ. |
Supplement | suppl. |
Volume | v. |
URI
Enter the Uniform Resource Identifier, when available. Include the protocol prefix e.g http:// and ftp://
Unlike web data formats, where HTML is an important one, but not the only one, and web protocols, where HTTP has a similar status, there is only one Web naming/addressing technology: URIs.
Uniform Resource Identifiers (URIs, aka URLs) are short strings that identify resources in the web: documents, images, downloadable files, services, electronic mailboxes, and other resources. They make resources available under a variety of naming schemes and access methods such as HTTP, FTP, and Internet mail addressable in the same simple way. They reduce the tedium of “log in to this server, then issue this magic command …” down to a single click.
Examples |
Type
Type
Meaning
The nature or genre of the content of the resource.
Objetive
Type helps describe the general categories, functions, genres, or aggregation levels for content of the resource.
Selecting Value for Type
Recommended best practice is to select a value from a controlled vocabulary (for example, the Dublin Core Type Vocabulary
To describe the physical or digital manifestation of the resource, use the dc:format element (See Format).
Other locally used “types” can also be included in this field.
Format : Extent, Medium
Format Extent
Meaning
The size or duration of the resource.
Objetive
Use this field to describe the physical extent of the documentary unit.
Guidance for adjusting code of Extent
It is important to realize that the volatility of remotely accessed electronic resources will cause the extent statements to change, for example when a word file is changed to XML.
Examples of digital resources
Type of resource |
Correct entry for Extent |
Description/Notes |
sound recordings | 28 min. | |
Online resources | 1 Web Site | |
Online resources | 1 Web Page | |
Word File | 345 KB | |
20 KB |
Format Medium
Meaning
The material or physical carrier of the resource.
Objetive
Format may be used to determine the software, hardware or other equipment needed to display or operate the resource.
Guidance for adjusting code of Medium
The internet media types[IMT] of the resource can also be used to indicate the hardware or software required to access the resource.
Language
Language
Meaning
A language of the intellectual content of the resource.
Objetive
This is used to indicate the language(s) in which the resource is available.
Selecting the Language
Language is a mandatory element for all types of resources, including those in which the text is only a summary.
Enter in this field a three-letter code (ISO639-2) or the two letter code (ISO639-1) to indicate the language in which the text of the item appears. If the resource contains more than one language, repeat the language element.
e.g.
ISO639-2 | ISO639-1 |
fin | fi |
swe | sv |
nor | no |
If a language does not have a code in the selected scheme, enter the full form of the language without indicating the scheme.
Parts of a whole
Record describing a whole resource containing separate articles, some in English, others in French.
e.g.
ISO639-2 | ISO639-1 |
eng | en |
fre | fr |
Relation
Relation
Meaning
A reference to a related resource.
Objetive
This allows the establishment of various relationships between resources and for users to locate related resources. This field is used to link one resource to another
Guidance for adjusting code of Relation
Recommended best practice is to reference the resource by means of standard identifier. Usually a URI conforming to a formal identification system.
Parts of a Whole
When the resource is a part of a whole, the information of the whole should be made available by providing a URI. If you have more information about the whole, put this information in the source field.
Relation Refinements
When using any of the following refinements, it is important to establish the type of relationship by choosing a value from one side of any of the following pairs of relation refinement types, shown in the following list:
Relation refinement | Description |
(DC) isPartOf | The described resource is a physical or logical part of the referenced resource. |
(DC) hasPart | The described resource includes the referenced resource either physically or logically. |
(DC) isVersionOf | The described resource is a version, edition, or adaptation of the referenced resource. Changes in version imply substantive changes in content rather than differences in format |
(DC) hasVersion | The described resource has a version, edition, or adaptation, namely, the referenced resource. |
(DC) isFormatOf | The described resource is the same intellectual content of the referenced resource, but presented in another format. |
(DC) hasFormat | The described resource pre-existed the referenced resource, which is essentially the same intellectual content presented in another format. |
(DC) references | The described resource references, cites, or otherwise points to the referenced resource. |
(DC) isReferencedBy | The described resource is referenced, cited, or otherwise pointed to by the referenced resource. |
(DC) isRequiredBy | The described resource is required by the referenced resource, either physically or logically. |
(DC) requires | The described resource requires the referenced resource to support its function, delivery, or coherence of content. |
(DC) isReplacedBy | The described resource is supplanted, displaced, or superseded by the referenced resource. |
(DC) replaces | The described resource supplants, displaces, or supersedes the referenced resource. |
4.13 Availability : Location, Number
4.13.1 Availability
Meaning
Availability provides users with the URI that is uniquely associated with an item, and serves to identify that item.
Objetive
To allow users to locate a particular item.
If the subject classification number is used to organize the Encyclopedia, place that number in Subject Classification element (see Subject Classification) leaving this field empty.
Source
Source (<dc:source />)
Meaning
A reference to a resource of which the current resource is a part.
Objetive
It provides additional information about the source of the resource.
Guidance for adjusting code of Source
Information that can go into this field includes the following:
- Title and subtitle
- Author
- Edition statement
- Place of publication
- Publisher
- Date of publication
- Standard number
Examples of citation information in the source element:
Examples |
Trekka round the world / John Guzzwell. // Great voyages in small boats. Clinton Corners, N.Y. : John de Graff, 1976. ISBN 0-8286-0079-1. p. 1-195 |
Coverage: Spatial, Temporal
Coverage
Meaning
The extent or scope of the content of the resource.
Objetive
This is used to provide information on coverage that includes spatial location (a place name or geographic coordinates), temporal period (a period label, date, or date range) or jurisdiction (such as a named administrative entity).
Guidance for adjusting code of coverage
Recommended best practice is to select a value from a controlled vocabulary (for example, the Legal Thesaurus and to use, where appropriate, named places or time periods in preference to numeric identifiers such as sets of coordinates or date ranges.
Coverage Temporal
Meaning
Temporal characteristics of the intellectual content of the resource.
Objetive
This is used to provide temporal periods (a period label, date, or date range)
Guidance for adjusting code of coverage
Recommended best practice is to select a value from recommended schemes.
Examples
DCMI PERIOD: A specification of the limits of a time interval
Example |
name=The Great Depression; start=1929; end=1939; Period name: The Great Depression start: 1929 end: 1939 |
W3C-DTF: W3C Encoding rules for dates and times – a profile based on ISO 8601
Example |
start=1999-09-25T14:20+10:00; end=1999-09-25T16:40+10:00; scheme=W3C-DTF; Period name: 1999 AFL Grand Final start: 1999-09-25T14:20+10:00 end: 999-09-25T16:40+10:00 |
Coverage Spatial
Meaning
Spatial characteristics of the intellectual content of the resource.
Objetive
This is used to provide information on coverage that includes spatial locations (a place name or geographic coordinates) or jurisdiction (such as a named administrative entity).
Guidance for adjusting code of coverage
Recommended best practice is to select a value from a controlled vocabulary (for example, the Legal Thesaurus or the Thesaurus of Geographic Names [TGN]) and to use, where appropriate, named places or time periods in preference to numeric identifiers such as sets of coordinates.
Encoding scheme
5 |
(DCTERMS) ISO3166: ISO 3166 Codes for the representation of names of countries.
Example |
spatial scheme: ISO3166 Ex. KE |
Rights: Statement, Terms of Use
Rights
Meaning
Information about rights held in and over the resource.
Objetive
To give information over owner of the rights terms of use of the information resource.
Guidance for adjusting code of Rights
This provides information on the copyright as well as access rights of the users to the resource.
If the Rights element is absent, no assumptions may be made about any rights held in or over the resource.
Rights Statement
Meaning
Written assertion of ownership rights relating to resource
Objetive
This is used to provide information on the ownership of the resource
Guidance for adjusting code of Rights Statement
Enter either a textual statement or a URL pointing to a rights statement, or a combination, when a brief statement and a lengthier one are available.
Examples |
Rights Statement: Rights=”http://lawin.org/tos” or/and Rights Statement: Lawi Copyright Information |
Rights Terms Of Use
Meaning
Extent and manner of use permitted to, and restrictions covering use of resource by the public
Objetive
This is used to provide information of the accessibility of any resource.
Guidance for adjusting code of Rights Terms of Use
Enter a statement that indicates the level of access to the resource.
Citation Identifier
Citation Identifier
Meaning
A global standard identifier of a law, case-law, legal doctrine of point of law. It is similar, in the case of a journal, of ISSN or other standards such as CODEN.
Objetive
This is a unique identifier of the law or case-law.
Guidance for adjusting code of citation Identifier
CELEX
CELEX is recorded in this field as the follow code (retain the hyphen).
Example | |
CELEX | 00000000 |
e
Alternative Identifier
Namespace | Type | Term | Scheme (example) | Identifier (example) | Description | Used by project | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
info:eu-repo | / | semantics | / | altIdentifier | / | doi | / | 10.1234-789.1 | alternative and persistent identifier of a resource | OpenAIREplus |
Supported Schemes
Scheme | Description |
---|---|
ark | Archival Resource Key |
arxiv | arXiv.org identifier |
doi | Digital Object Identifier |
hdl | Handle Identifier |
isbn | International Standard Book Number |
issn | International Standard Serial Number |
pmid | PubMed ID |
purl | Persistent Uniform Resource Locator |
urn | Uniform Resource Name |
wos | Web of Science accession number |
Reference Identifier
Namespace | Type | Term | Scheme (example) | Identifier (example) | Description | Used by project | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
info:eu-repo | / | semantics | / | reference | / | urn | / | urn:nbn:de:123-4567890 | reference identifier of a publication mentioned in a given publication resource | OpenAIREplus |
Supported Schemes
Scheme | Description |
---|---|
ark | Archival Resource Key |
arxiv | arXiv.org identifier |
doi | Digital Object Identifier |
hdl | Handle Identifier |
isbn | International Standard Book Number |
issn | International Standard Serial Number |
pmid | PubMed ID |
purl | Persistent Uniform Resource Locator |
url | Uniform Resource Locator |
urn | Uniform Resource Name |
wos | Web of Science accession number |
Versions
The XML schema can be found here using this link: http://purl.org/info:eu-repo/schemas/xmls/2010/05/07/versionTypes.xsd | NOTE: only the types are included used by the DRIVER project |
Namespace | Type | Term | Description | Used by project | ||||
---|---|---|---|---|---|---|---|---|
info:eu-repo | / | semantics | / | publishedVersion | NEEO | |||
info:eu-repo | / | semantics | / | authorVersion | NEEO | |||
info:eu-repo | / | semantics | / | draft | Early version circulated as work in progress | DRIVER | ||
info:eu-repo | / | semantics | / | submittedVersion | The version that has been submitted to a journal for peer review | DRIVER | ||
info:eu-repo | / | semantics | / | acceptedVersion | The author-created version that incorporates referee comments and is the accepted for publication version | DRIVER | ||
info:eu-repo | / | semantics | / | publishedVersion | The publisher created published version | DRIVER | ||
info:eu-repo | / | semantics | / | updatedVersion | A version updated since publication | DRIVER |
Leave a Reply