|
Forced Migration Online
DIGITAL LIBRARY: CATALOGUING GUIDELINES - v.11 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The purpose of this document is to provide step-by-step instructions for entering information into each of the elements (or fields) that are represented in the Digital Library (DL). Introduction 1.1 Using the Cataloguing Web Form Please refer to the separate instructions for accessing the web forms needed to add records to the DL. 1.2 Standards Used in the Digital Library The elements (or fields) represented in the DL are based on the metadata standards developed by the Dublin Core Metadata Initiative (http://www.dublincore.org). All 15 elements included in the core set are represented, along with one non-Dublin Core field (“note”). An additional 15 qualifiers or sub-elements have been defined that cater to the particular needs of the DL; seven of these conform to the Dublin Core qualifier set recommendations. The table below summarizes the elements and sub-elements used in the Digital Library and notes the origin of each.
Other standards were used to develop the various controlled lists used by digital library. The most significant ones include: - Geographic terms (for coverage.geography): Microthesaurus of Geographical Terms (HURIDOCS) at http://www.huridocs.org/mt15.htm - Micro-Thesaurus 14: Languages (HURIDOCS, 2001) (http://www.huridocs.org/mt14.htm) - Subject terms: International Thesaurus of Refugee Terminology (UNHCR). 1.3 Required fields Of the 27 fields represented in the DL, 11 are required. In other words, they must have data entered into them in order for the record to be considered complete. The guidelines below indicate which fields are mandatory and which are optional. In addition, the table in Annex 1 lists all required fields. 1.3 Multiple occurrences The guidelines below indicate the maximum number of occurrences for each DL field. For example, cataloguers may enter up to 15 creators, 15 subject (controlled) terms, and 15 languages per document. However, cataloguers are not obligated to fill in every occurrence of a field; rather, the multiple field occurrences are available simply to provide the cataloguer with an opportunity to enter information that is as complete as possible. The table in Annex 1 notes the maximum number of occurrences for each field. 1.4 Multilingual aspects The objective of the DL is to develop an international and multilingual collection of resources. However, to be truly global will require proceeding in a step-wise fashion. In the initial stages of development, the DL will provide access to resources in multiple languages, but the interface for searching and browsing the catalogue will remain in English for the time being. At the same time, simply providing access to resources in various languages can be challenging from a technical point of view and therefore has ramifications for the cataloguing process. The following fields can have non-English information entered into them: - title - alternative title - creator - contributor - publisher Xdirectory, the content management system used by FMO for cataloguing purposes, is UNICODE-compliant and therefore supports the entry and display of both Roman and non-Roman characters. Alternatively, editors may copy and paste non-English terms describing a resource into the cataloguing web form. All other fields besides those enumerated above are designated as English-only fields, again for the time being. The table in Annex 1 below lists which fields are multilingual vs. English-only. Guidelines 2.1 Basic Details about the Document DLTitle required Ø The formal name of the resource. Enter the title as it appears on the resource, using the original language, wording, order and spelling. In general, capitalize the first word of the title; enter all other words in lower case except proper nouns and acronyms. (German-language titles are an exception since all nouns are written with an initial cap. Enter these as they would appear in a normal sentence.) Enter a maximum of one title. If a resource appears to have more than one title, use your judgment to select the most logical and appropriate one. Examples: On the document: GUIDE PRATIQUE DU JOURNALISTE DLTitle entry: Guide pratique du journaliste On the document: The Protection of Refugees and IDPs in Serbia DLTitle entry: The protection of refugees and IDPs in Serbia On the resource: Wie es ist, ein Flüchtling zu sein DLTitle entry: Wie es ist, ein Flüchtling zu sein Ø Conventions, protocols, charters, constitutions, legislative acts, pacts, plans, treaties and other international instruments are exceptions to this rule. Use title case with these documents. Example: On the document: Universal Declaration of Human Rights DLTitle entry: Universal Declaration of Human Rights Ø Subtitles should be separated from the main title by a <colon> and <space>. Example: On the document: The State of the World's Refugees: The Challenge of Protection DLTitle entry: The state of the world's refugees: the challenge of protection Ø If the resource does not appear to have a title or if the title that does exist does not refer logically to the resource, then supply a title and enclose it in square brackets [ ]. Examples: On the document: By Country DLTitle entry: [Information on complex emergencies and natural disasters by country] Ø Bilingual (or parallel) titles should be separated by a <space> <=> <space>. Example: On the document: L'asile dans le systeme inter-americain / Asylum in the Inter-American System DLTitle entry: L'asile dans le systeme inter-americain = Asylum in the inter-American system DLAlternativeTitle Ø If applicable, enter an alternative title which is commonly used as a substitute for the main title, i.e., abbreviated titles, translated titles, etc. Series information may also be entered here, if it is presented as part of the title. Enter a maximum of three alternative titles. Example: DLTitle entry: Handbook on procedures and criteria for determining refugee status under the 1951 Convention and 1967 Protocol relating to the Status of Refugees DLAlternativeTitle entry: UNHCR handbook DLIdentifier required Ø The unique identifier for the document being described. In the DL, this will be the barcode assigned to the document after it has been scanned. Note: If the document being catalogued has not yet been scanned, the cataloguer will not be able to complete the identifier field in the early stages of the cataloguing process; therefore, s/he will need to return at a later point in time to enter this information. Example: DLTitle entry: The challenges of meeting the psychosocial needs of refugees in Sweden: seminar at Refugee Studies Programme, University of Oxford, 26 February 1992 Barcode on document: 3028377962 DLIdentifier entry: 3028377962 DLIdentifierShelfmark Ø The code assigned to the document that identifies its physical location within the library collection of the contributing institution. The shelfmark scheme actually used will vary from library to library. The purpose for including this is to give the user sufficient information to be able to examine the original version of the document, if s/he chooses. Ø Note, though, that some documents may be "born digital," in which case they will not have original print counterparts. Example: DLTitle entry: Population resettlement and development DLIdentifierShelfmark entry: RSC/A-56 CER DLIdentifierInstitution required Ø The code representing the institution contributing a document to the DL. Select from a controlled list (e.g., AUC, CHC, COL, RSC, TUF, etc.) 2.2 Entities Responsible for the Document DLCreator required Ø The person(s) or organization(s) primarily responsible for the creation of the document. Enter personal creators as follows: surname <comma><space>first name(s) and/or initials. Omit titles and terms of relation (e.g., Dr., Jr., etc.). Enter a maximum of 15 creators. When in doubt, follow the more detailed guidelines provided in HURIDOCS Supporting Document A (http://www.huridocs.org/popnames.htm). Examples: Name on document: Nick Van Hear DLCreator entry: Van Hear, Nick Name on document: Dr Barbara Harrell-Bond DLCreator entry: Harrell-Bond, Barbara Name on document: Theo E.M. Thompson DLCreator entry: Thompson, Theo E.M. Name on document: Kwok Bun Chan DLCreator entry: Chan, Kwok Bun Name on document: Abdullah Ahmed AN-NA'IM DLCreator entry: An-Na'im, Abdullah Ahmed Names on document: Richard Black and Thomas Mabwe DLCreator entry: Black, Richard DLCreator entry: Mabwe, Thomas Ø Enter corporate creators as written and in the language indicated on the document. Capitalize the first letter of each significant word in the name. Omit initial articles (e.g., the, le, etc.). If the organization is commonly referred to by its acronym, include it in parentheses. If the corporate creator appears in more than one language, enter the one that is provided in the language of the document being described. Examples: DLCreator entry: Instituto del Tercer Mundo DLCreator entry: Heidelberger Institut für Internationale Konfliktforschung DLCreator entry: United Nations High Commissioner for Refugees (UNHCR) Ø If the corporate creator is associated with a particular place or if it is a fairly generic title, enter a place name in brackets [ ]. Refer to the Microthesaurus of Geographical Terms (HURIDOCS) at http://www.huridocs.org/mt15.htm for assistance. Example: DLCreator entry: Lawyers for Human Rights [South Africa] DLCreator entry: Directorate of Immigration [Finland] Ø If the document indicates that the corporate creator is a part of or subordinate to another body (e.g., Department, Division, Service, Committee, Section, Bureau, etc.), then enter the higher corporate body first, followed by the subordinate body. The form used is as follows: higher corporate body<period><space>subordinate corporate body. Examples: On the document: The research group on forced migration Department of Geography Norwegian University of Science and Technology DLCreator entry: Norwegian University of Science and Technology. Department of Geography. Research Group on Forced Migration Ø If only an acronym is indicated on the document, attempt to locate and record the full name of the organization. Example: Name on document: ECRE DLCreator entry: European Council on Refugees and Exiles (ECRE) Ø If no creator is indicated, enter the corporate body responsible for making the resource available (i.e., the publisher). Example: Title entry: L'immigration et le droit d'asile DLCreator entry: Sénat [France] DLContributor Ø A person or organization not specified in the creator element who has made a significant contribution to the document but whose contribution is secondary (e.g., translator, illustrator, etc.). Use the instructions provided for "creator" for entering information in this field. Indicate the role played by the contributor in brackets [ ]. Enter a maximum of 15. Example: Title entry: Annotated bibliography on Palestinian women DLContributor entry: Baumann, Pari [compiler] DLPublisher Ø The entity responsible for making the resource available in its present form, such as a publishing house, university department, or corporate body. Use the instructions provided for "creator" for entering information in this field. Enter a maximum of 15 publishers. Ø Note: Because most of the documents represented in the Digital Library fall into the category of grey literature and therefore are considered unpublished, this field may not prove to be very relevant at first. However, over time, we will be adding published journal articles to the collection. Examples: DLTitle entry: Outside the protection of the law: the situation of irregular migrants in Europe DLCreator entry: Gibney, Matthew DLPublisher entry: Refugee Studies Centre (RSC) DLPublisherType Ø Identifies the type of entity responsible for making the resource available (e.g., NGO, IGO, academic institute, etc.). Select from the following controlled list. Enter a maximum of 15.
Ø Enter the URL of the publisher's home page, if indicated. Include http:// at the beginning of the URL. Enter a maximum of 15. 2.3 Document Content DLDescription Ø The description helps the user to quickly determine the relevance of a document and whether or not it contains important features. Include the table of contents, if one is provided, or make note of the main sub-headings. Also, make note of any important annexes like bibliographies or glossaries. Enter any additional information about the document that is not available in other fields but that may be considered particularly useful to the user (e.g., the name of the conference that a paper was presented at, etc.). Do not evaluate the resource. This field is not intended to function as a "book" review. Example: DLTitle entry: Guide to international refugee law resources on the web DLCreator entry: Mason, Elisa DLDescription entry: This guide was prepared for participants attending the annual "Law of Refugee Status" workshop sponsored by the Refugee Studies Centre. It includes sections on "international instruments," "international bodies," "national legislation," "case law," "journals," "bibliographic tools and research guides," and "NGOs." Each section highlights examples of web sites that either provide access to the full texts of these sources or serve as useful contacts for more information. DLLanguage required Ø The language of the individual document being catalogued. Select the three-letter language code from a controlled list. If the document is in more than one language, enter the relevant codes. Enter a maximum of 15 languages. (Refer to HURIDOCS' Micro-Thesaurus 14: Languages at http://www.huridocs.org/mt14.htm for assistance.) Examples: DLTitle entry: Les réfugiés apolitiques: guerre civile et persecution de groupe au regard de la Convention de Genève DLLanguage entry: FRE DLTitle entry: Women refugees = Femmes réfugiées = Mujeres refugiadas DLLanguage entry: ENG DLLanguage entry: FRE DLLanguage entry: SPA DLSubjectControlled required Ø Enter terms that describe the document. Enter up to a maximum of 15 focused terms that describe the main concepts of the document. These can be identified from the title, table of contents, introduction, and/or conclusion. Ø To help you determine which subject keywords to select, ask yourself some basic questions about the main concepts of the resource, such as who, what, what kind of, why, by whom. Examples include: (1) "who" does the document focus on (i.e., specific types of forced migrants like internally displaced persons or women refugees; specific ethnic and national groups, like Tamils; specific religious, social or political groups, etc.); (2) "what" does the document concern itself with (i.e., specific causes of flight like development-induced displacement; specific responses to forced migration situations like protection or assistance; specific country of origin conditions; repatriation or return; specific experiences of forced migrants like psychosocial or integration issues); (3) asking "what kind of" and "why" can help to specify the "what" (e.g., a document that discusses humanitarian assistance for displaced persons in Sudan might include the keywords "food supply" and "famine"); (4) "by whom" refers to the actors (institutions, organizations) that act on behalf of the "who" – IGOs, NGOs, etc. Ø The average number of terms entered will most likely be four to five. Ø Select terms from the International Thesaurus of Refugee Terminology. Words should be entered with an initial cap. Examples: DLTitle entry: Saving lives and livelihoods: the fundamentals of a livelihoods strategy DLSubject entry: Emergency relief DLSubject entry: Refugee aid & development DLSubject entry: Dependency DLSubject entry: NGOs DLSubject entry: Coordination DLSubject entry: Management DLSubject entry: Policy making DLSubject entry: Social participation DLSubject entry: Self-sustaining projects DLSubjectUncontrolled Ø Use this field to enter terms for subject areas not covered by the International Thesaurus of Refugee Terminology. Another thesaurus that is more relevant may be referred to; this will help ensure that terms are entered in a standard way. Enter a maximum of 10 uncontrolled terms. Ø The resulting list will be evaluated and eventually incorporated into a controlled format in the future. DLSubjectClass Ø A broad subject term that represents the subject matter of the document as a whole. This will determine in which section of FMO the resource will appear for browsing purposes. Select from a controlled list. Documents may be classified under a maximum of three subjects. [NOTE: THIS FIELD HAS BEEN TEMPORARILY DISCONTINUED.] DLCoverageGeography required Ø The spatial extent or scope of the document. Select a place name for countries and/or regions from a controlled list (refer to HURIDOCS' Micro-thesaurus: Geographical Terms at http://www.huridocs.org/mt15.htm for assistance). If the document does not focus on a particular country or region, select "universal" from the controlled list. Enter a maximum of ten geographic terms. Examples: DLTitle entry: Dados estatísticos DLCoverageGeography entry: Portugal DLTitle entry: Children, war and psychological intervention DLCoverageGeography entry: Universal DLCoverage Time Ø The temporal extent or scope of the document. Enter a maximum of one period or date range (e.g., 1960-1969). Example: DLTitle entry: Population displacement, state-building and social identity in the lands of the former Russian Empire, 1918-1930 DLCoverageTime entry: 1918-1930 2.4 Resource Dates DLDateCreated required Ø Enter the year when the document was first created or published. Use the form 01/01/YYYY, as indicated in the example below. (Note: This form differs from the webcat!!) This format must be used to ensure that dates are properly converted when imported into the Olive system that houses the digital library repository! Ø If no date is indicated, provide a best guess by examining the document, particularly any bibliographic references that are included. Do not insert [] around the date if it is estimated, even though this would be consistent with cataloguing practices. The system is not able to interpret square brackets in the date field. Examples: DLTitle entry: Refugees: the future of international law and organization Date on title page: May 1988 DLDateCreated entry: 01/01/1988 DLTitle entry: Droits des femmes en situations de conflit = Women's rights in conflict situations Date on title page: 1999 DLDateCreated entry: 01/01/1999 DLDateReliable required Ø An indication of whether the Date Created is reliable. Since many grey literature documents do not include dates, the editor may need to provide a best guess, as noted above. Select "Yes" if a date was provided on the document, or "No" if the date was estimated. 2.5 Document Type, Form and Relationship to Other Resources DLType required Ø The category of the document (e.g., conference paper, training materials, bibliography, etc.). A series of document types has been pre-defined. Select from a controlled list. Enter a maximum of five types. Example: DLTitle entry: Dams, displacement, policy and law in India DLType entry: Conference papers DLRelation Ø Indicate the relationship of the described document to any other information source. For example, an article within a journal, a title within a series, a paper presented at a conference, edition details, etc. Include the volume/issue and page numbers, if available. Enter a maximum of five occurrences. Ø If the document is a journal article, use the form provided in the example below. Examples: DLTitle entry: Protection against expulsion under article 3 of the European Convention on Human Rights DLRelation entry: European Journal of International Law 4(3): 303-423. DLTitle entry: An international legal perspective on refugee and displaced women DLRelation entry: paper presented at the Regional Conference on the Legal Status of Refugee and Internally Displaced Women in Africa, Addis Ababa, 1-4 Aug 1995 DLRelationRequires Ø Indicate what the document being described needs in order for it to be used, viewed, or navigated effectively. For now, this will be limited to entering "Adobe Acrobat" since most of the documents in the Digital Library will be made available as PDF files for printing purposes. In the future, if other types of resources are included in the DL such as images, then another type of plug-in might be required. DLFormatMedium Ø The media type of the document as it appears in the digital library (e.g., pdf, video, audio, jpeg, etc.). Again, for the time being, “GIF” and "PDF" will be the primary formats entered into this field. Select both from a controlled list. DLFormatExtent Ø The size or duration of the document (e.g., number of pages, length of audio or video). If this information is not indicated on the unit, count or estimate the length and record the entry in square brackets. Examples: DLFormatExtent entry: 30 p. DLFormatExtent entry: [67] p. DLFormatExtent entry: All audio segments are 4 minutes or less in length. DLSource Ø If applicable, a work from which the document was derived. Enter a string or number used to uniquely identify the work (e.g., an ISBN or ISSN number if the resource is an electronic version of a printed book or journal). Enter a maximum of three sources. Example: DLTitle entry: The age of humanitarian emergencies DLSource entry: ISBN 952-9520-39-5 2.6 Use of the Document DLRights required Ø An indication of the copyright clearance for the individual document. This information will be entered at a later point in time, and not necessarily by the cataloguer. Select from a controlled list (i.e., cleared, best endeavour). 2.7 Other DLNote Ø The note field is used for any additional comments or information that the cataloguer feels is important to log; it is a “housekeeping” field, i.e., one that will not be visible to the user, and will also be used to accommodate notes maintained in Cardbox (the RSC library catalogue). 2.8 System Metadata This section reviews the 13 xdirectory fields that are automatically appended to every record after "Rights." Ignore the following fields:
Status required Six statuses are available: Live, Incomplete, Pending Editor, Olive, Scanning, and Withdrawn. Ø If you are interrupted during a cataloguing session, set the record status to "incomplete" and save the record. Note: The system will remind you to assign the record to a category, so be sure to tick "digital library" before exiting the record. Ø If you are a cataloguer and you have completed a new record, set the record status to "pending editor" and save the record. Ø If you are an editor and you have completed a record, set the record status to "live" and save the record. Note: You must have a date entered into the "information correct" field or the system will not allow you to designate the record as live. Ø The statuses "Olive" and "Scanning" are used by the coordinator of the digital library to help her with workflow tracking. Contributor Review Date Ø The date when a document should be reviewed for updating purposes. This field is not as relevant to the digital library; however, there may be a case when an author indicates that a document will be revised by a particular date. This field could be used to record such information. Ø The system defaults to a review date within a year, as shown in the example below. IMPORTANT NOTE: If you do enter a different date, it must be entered in the European format!!! This is dictated by xdirectory and cannot be changed!!! The format is: mm/dd/yy. Example: Date that record was added to webcat: 30 May 2002 Contributor review date: 30/05/03 Info Correct Date required Ø The date for which the accuracy of the record was last checked. Enter the date that the record was added to the DL. IMPORTANT NOTE: A date must appear in this field in order for the record to be set to "live" status. In addition, this date must be entered in the European format!!! This is dictated by xdirectory and cannot be changed!!! The format is: mm/dd/yy. Administrators Comments Ø Enter any notes about the cataloguing process or reminders to yourself regarding record data. This field will not be visible to the public. Categories required Ø Tick the box under "Digital Library" in order to ensure that the record appears in the system. Conclusion In the end, cataloguers must use their best judgment when describing documents! The rules outlined above are not set in stone, but rather are presented for guidance purposes. It is impossible to predict every scenario that might be encountered, particularly with grey literature. The important thing to keep in mind is that the purpose of the catalogue record is to provide sufficient information for the user to (1) locate the document in the catalogue, and (2) determine whether or not a document is worth viewing. Further Information Dublin Core Metadata Initiative – http://www.dublincore.org Huridocs Standard Formats for the Recording and Exchange of Bibliographic Information Concerning Human Rights - http://www.huridocs.org/standard.htm Introduction to Metadata: Pathways to Digital Information - http://www.getty.edu/research/institute/standards/intrometadata/index.html
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||