Home » Proposal » Dublin core elements for thesis proposal

Dublin core elements for thesis proposal

Dublin core elements for thesis proposal Notes              
   Additionally towards the

Network Development and MARC Standards Office
Library of Congress

Date issued: 2008-04-23

I. Introduction

This is often a crosswalk relating to the metadata terms within the Dublin Core Element Set and MARC 21 bibliographic data elements. The crosswalk can be utilized for conversion of Dublin Core metadata into MARC, as an instrument for developing XSLT transformations. For conversion of MARC 21 into Dublin Core, the MARC to Dublin Core Crosswalk must be used, since during this conversion many fields are mapped in a single Dublin Core element.

Within the Dublin Core to MARC mapping, two mappings are supplied, one for unqualified Dublin Core elements (i.e. the primary 15 elements much like Dublin Core Metadata Element Set, version 1.1 ) but another for qualified (individuals in addition that appear only in DCMI Metadata Terms ). The second includes both refinements within the original 15 furthermore to syntax and vocabulary encoding schemes.

MARC 21 fields are listed with field number, then two indicator values with field name/subfield name in parentheses. If both field and subfield have similar name, the subfield name isn’t incorporated. A obvious (H’20’) is suggested with this particular document by #. The label could be a shortened type of the element name.

Definitions are acquired from Dublin Core Metadata Element Set, Version 1.1: Reference Description. To learn more about Dublin Core elements, including application notes (succumbed Comment), reference that document. All Dublin Core elements are optional and repeatable. During this document elements are listed in the to z by Dublin Core label.

II. Dublin Core to MARC Crosswalk (15 elements in version 1.1 and refinements)

Contributor — A business accountable for making contributions for that resource.

Dublin core elements for thesis proposal record comes from Dublin

  • Unqualified:
    • 720 ##$a (Added Entry–Unmanageable Name/Name)
  • Qualified:
    • Element refinements can be utilized inside the MARC relator list for individuals specified roles that refine electricity:contributor. If Electricity metadata features a role refinement (only helpful for Contributor), make use of the term in 720$e or possibly the code in 720$t. See: MARC Relator Terms and Dublin Core

Note: there’s no chance to specify once the Contributor could be a person or organization because it is in the Dublin Core data. Whether it can reasonably be figured that the contributor could be a person or organization, fields 700 1#$a (Added Entry–Personal Name) or 710 2#$a (Added Entry–Corporate Name) can be utilized.

Coverage — The spatial or temporal subject within the resource, the spatial applicability within the resource, or possibly the jurisdiction he resource is relevant.

  • Unqualified:
    • 500$a (General note)
  • Qualified:
    • Spatial: 522 ##$a (Geographic Coverage Note)
    • Temporal: 513 ##$b (Kind of Report and Period Covered Note/Period covered)
  • Syntax encoding schemes:
    • Box: 507$a (Scale Note for Graphic Material)
    • ISO3166: 043$c with $2 iso3166 (Geographic Area Code/ISO code)
    • Point: 507$a (Scale Note for Graphic Material)
  • Vocabulary encoding plan under spatial:
    • TGN: 651 #7 $a (Subject Added Entry–Geographic Name) with $2=tgn
    • Period: 045 # $b (Duration of Content/Formatted 9999 B.C. through C.E. period of time)

    Dublin core elements for thesis proposal If both field and

Creator — A business mainly accountable for making the resource.

  • Unqualified:
    • 720 ##$a (Added Entry–Unmanageable Name/Name) with $e=author

Note: there’s no chance to specify once the Creator could be a person or organization because it is in the Dublin Core data. Whether it can reasonably be figured that the Creator could be a person or organization, fields 100 1#$a (Primary Entry–Personal Name) or 110 2#$a (Primary Entry–Corporate Name) can be utilized for the first Creator, and 700 1#$a (Added Entry–Personal Name) or 7102#$a (Added Entry–Corporate Name) persons can be utilized.

Date — An area or time period connected through getting a meeting within the lifecycle within the resource.

  • Unqualified:
    • 260 ##$c (Date of publication, distribution, etc.)
  • Qualified:
    • Available: 307 ##$a (Hrs, Etc.)
    • Produced: 046$k (Special Coded Dates/Date produced)
    • Date Recognized: 502##$a (Dissertation Note) with initial label Date recognized
    • Date ed: 260##$c (Date of publication, distribution, etc.) or 542 $g (Information Associated with Status/ date) Note: internet search engine optimization was defined in MARC inside the month from the month of the month of january 2008. Prefer 542 if field might be acquired.
    • Date Printed: 502##$a (Dissertation Note) with initial label Date printed
    • Issued: 260 ##$c (Date of publication, distribution, etc.)
    • Modified: 046##$j (Special Coded Dates/Date modified)
    • Valid: 046##$m (Special Coded Dates/Date valid)
  • Syntax encoding schemes:
    • Period: 045##c (Special Coded Dates/Date 1, C.E. date)
    • W3CDTF: 260 ##$c (Date of publication, distribution, etc.) date can also be generated in 008/07-10 see below under Notes. Remove hyphens in 008.

Description — A foreign exchange account within the resource.

  • Unqualified:
    • 520 ##$a (Summary, etc. note)
  • Qualified:
    • Abstract: 520 ##$a (Summary, etc. note)
    • TableofContents: 505 #$a (Formatted Contents Note)

Format — The extendable, physical medium, or size the resource.

  • Unqualified:
    • 856 ##$q (Electronic Location and Access/E-mail type)
  • Qualified:
    • Extent: 300 ##$a (Physical Description)
    • Medium: 340 ##$a (Physical Medium)
  • Syntax encoding plan:
    • IMT: 856 ##$q (Electronic Location and Access/E-mail Type)

Identifier — An unambiguous mention of the resource within the given context.

  • Unqualified:
    • If string begins : 856 40 $u (Electronic Location and Access/URI)
    • Otherwise: 024 8#$a (Other Standard Identifier/Standard number or code)
  • Qualified:
    • Bibliographic Citation: 500 ##a (General note) with initial label Bibliographic citation
  • Syntax encoding plan:
    • URI: 856 40$u (Electronic Location and Access/Uniform Resource Locator)

Note: some other type of identifiers (e.g. ISSN, ISBN) might be expressed by means of URIs in electricity:identifier.

Language — A language within the resource.

  • Unqualified:
    • 546 ##$a (Language note)
  • Qualified:
  • Syntax encoding schemes:
    • ISO 639-2: 0410#$a (Language code)
    • RFC 1766: 041 07$a (Language code) with $2=rfc1766
    • RFC 3066: 041 07$a (Language code) with $2=rfc3066
    • RFC 4646: 041 07$a (Language code) with $2=rfc4646

Author — A business accountable for making the resource available.

  • Unqualified:
    • 260 ##$b (Publication, Distribution, etc. (Imprint)/Name of author, distributor, etc.)

Relation — An connected resource.

  • Unqualified:
    • 787 #$n (Nonspecific Relationship Entry/Note)
  • Qualified:
    • URI (Encoding plan): 787 #$o (Nonspecific Relationship Entry/Other identifier)
    • Conforms To: 787 #$n (Nonspecific Relationship Entry/Other identifier) with $i=Conforms to
    • HasFormat: 776 #$n (Additional Physical Form Entry/Note)
    • HasFormat: (Plan=URI): 776 #$o (Additional Physical Form Entry/Other identifier)
    • IsFormatOf: 776 #$n (Additional Physical Form Entry/Note)
    • IsFormatOf: (Plan=URI): 776 #$o (Additional Physical Form Entry/Other identifier)
    • IsPartOf: 773 #$n (Host Item Entry/Note)
    • IsPartOf (Plan=URI): 773 #$o (Host Item Entry/Other identifier)
    • HasPart: 774 #$n (Constituent Unit Entry/Note)
    • HasPart (Plan=URI): 774 #$o (Constituent Unit Entry/Other identifier)
    • IsVersionOf: 775 #$n (Other Edition Entry/Note)
    • IsVersionOf (Plan=URI): 775 #$o (Other Edition Entry/Other identifier)
    • HasVersion: 775 #$n (Other Edition Entry/Note)
    • HasVersion (Plan=URI): 775 #$o (Other Edition Entry/Other identifier)
    • Draws On: 786 #$n (Databases Entry/Note)
    • Draws On (Plan=URI): 786 #$o (Databases Entry/Other identifier)
    • Is Referenced By: 510 #$a (Citation/References Note/Name of source)
    • Requires: 538 ##$a (System Details Note)
    • Is Needed By: 787 #$n (Nonspecific Relationship Entry/Other identifier) with $i=Is needed by
    • Replaces: 780 00$n (Preceding entry)
    • Replaces (Plan=URI): 780 00$o (Preceding entry)
    • Is Substituted With: 785 00$n (Succeeding entry)
    • Is Substituted With (Plan=URI): 785 00$o (Succeeding entry)
    • References: 787 #$n (Nonspecific Relationship Entry/Other identifier) with $i=References
    • References (Plan=URI): 787 #$o (Nonspecific Relationship Entry/Other identifier) with $i=References

Legal legal legal rights — Specifics of legal legal legal rights stored in along with within the resource.

  • Unqualified:
    • 540 ##$a (Terms Governing Use and Reproduction Note)
  • Qualified:
    • Access Legal legal legal rights: 506##$a (Limitations on Access Note)
    • License: 540##$a (Terms Governing Use and Reprofuction Note
    • License (if value could be a URI): 540##$u

Source — An connected resource the described resource comes.

  • Unqualified:
    • 786 #$n (Databases Entry/Note)
  • Qualified:
  • Syntax encoding plan
    • URI. 786 #$o (Databases Entry/Other identifier)

Subject — The subject within the resource.

  • Unqualified:
    • 653 ##$a (Index Term–Unmanageable)
  • Qualified:
  • Vocabulary encoding schemes:
    • DDC: 082 ##$a (Dewey Decimal Call Number/Classification number)
    • LCC: 050 ##$a (Library of Congress Call Number/Classification number)
    • LCSH: 650 #$a (Subject added entry–Topical term)
    • MeSH: 650 #2$a (Subject added entry–Topical term)
    • UDC: 080 ##$a (Universal Decimal Classification Number)

Title — A standing given to the resource.

  • Unqualified:
    • 245 00$a (Title Statement/Title proper)
    • If repeated, all titles carrying out a first: 246 33$a (Different of Title/Title proper)
  • Qualified:
    • Alternative: 246 33$a (Different of Title/Title proper)

Type — The level of smoothness or genre within the resource.

  • Unqualified:
    • 655 #7$a (Index Term–Genre/Form) with $2=local
  • Qualified:
    • DCMI Type vocabulary (Encoding plan): 655 #7$a (Index Term–Genre/Form) with $2=dct

See Section III to be used to uncover Leader/06 (Kind of Record) values.

III. Additional Dublin Core Elements

  • Accrual Method: 541##$c (Method of getting Acquisition Note)
  • Accrual Periodicity: 310##$a (Current Publication Frequency)
  • Audience: 521##$a (Audience Note)
  • Education Level: 521##$a (Audience Note)
  • Provenance: 561##$a (Possession and Custodial History)

IV. Notes

In addition for that variable length fields indexed by the mapping, a MARC 21 record may also give a Leader and field 008 (Fixed-Length Data Elements). Certain character positions in many these fixed length fields in the USMARC record should be coded, although most will generate default values.

Leader: a group field like the first 24 character positions (00-23) of each record that gives information for the processing within the record. The next positions must be generated:

  • Character Position 06: Kind of record
    Leader/06 value must be set based on value in Type the following (these values result from Dublin Core Set of Resource Types (Electricity Type Vocabulary):

If no type is indicated, use value a. If two type values are indicated, and one of those is collection make use of the other value for setting Leader/06. If greater than two, use m.

  • Character Position 07: Bibliographic level
    • If Type value is collection, use value c (Collection)
    • Others, use value m (Monograph).
  • Character Position 08: Kind of control
    • Use value #” (blank: no specific kind of control).
  • Character Position 09: Character coding plan
    • Use value # (blank: MARC-8).
  • Character Position 17: Encoding level
    • Use value 3 (Abbreviated level) or any other value as appropriate to application
  • Character Position 18: Descriptive cataloging form
    • Use value u (Unknown) to point out the descriptive cataloging form is unknown.

008 Fixed Length Data Elements: Forty character positions (00-39) containing positionally-defined data factors that provide coded specifics of the record generally or about special bibliographic regions of the item being cataloged. For records originating as Dublin Core, the next character positions are utilized:

  • Character positions 00-05: Date the MARC 21 record was produced or converted (generate by date record grew to become part of system formatted as YYMMDD)
  • Character positions 07-10: Date of Publication (YYYY portion from Date if there is any). Qualified Electricity: Date.Issued in ISO 8601 (only YYYY portion).
  • Character positions 35-37: Language. Might be produced by data in Language if plan=ISO 639-2.
  • Other character positions can default to fill figures (ASCII 7C)

042$a Authentication Code. Use electricity (identifies that MARC 21 record arises from Dublin Core style record).

IV. Purposes of mapping Dublin Core to MARC

A mapping relating to the elements within the Dublin Core and MARC 21 fields is essential to make certain that conversions between various syntaxes can happen precisely. Once Dublin Core style metadata is broadly provided, it could speak with MARC records in many ways which follow:

Enhancement of straightforward resource description record. A cataloging agency should extract the metadata provided in Dublin Core style and convert the information elements to MARC 21 fields, developing a skeletal record. That record might then be enhanced as needed to include additional information generally provided within the particular catalog. Some projects convert data and make use of as fundamental record for reporting to national bibliography.

Searching across syntaxes and databases. Libraries have large systems with valuable information in metadata records in MARC format. It will be needed for systems so that you can search metadata in a number of syntaxes and databases and have commonality within the definition and make use of of elements. A principal use using this mapping is fantastic for harvesting metadata records from various sources, where there might be necessary to translate Dublin Core records to MARC or the opposite way round.

Share this:
custom writing low cost
Order custom writing