Converting CODEN to Inspire


SPIRES' CODEN db contains 3299 records with information about journals like CODEN, publisher, title variants. In Inspire, this db will serve as an authority file. But most library catalogues treat journals as bibliographic records. Couldn't find an example to copy from. Many fields in the proposal below are somewhat arbitrary


Some possible uses:

  • kb for refextract
  • autocomplete in bibedit
  • "published" status of HEP records
  • kb for CODEN translation
  • kb for ingestion of publishers feeds, arxiv harvesting

Field Mapping (new)

MARC tag subfield element notes
022 a ISSN  
  b material electronic/printed
030 a CODEN  
2100 a Inspire short title  
  2   "INSPIRE"
2227 a Inspire long title  
  2   "INSPIRE"
245 a journal-title ZDB title
2463 a Inspire long title  
247 a former title  
260 b publisher  
500 a public note  
540 a OA tag, license  
  u url  
547 a history  
590 a nonpublic note  
5830 a journal handling e.g. complete coverage
730 a title variants  
78002 w recid superseded record
  x ISSN  
78502 w recid superseding record
  x ISSN  
8564 u url  
909CO a OAI id  
915 a peer review tag  
980 a JOURNAL  
980 a BookSeries  
981 a recid of merged record  
-- AnnetteHoltkamp - 10 Apr 2014

Field Mapping (current)

MARC tag subfield SPIRES elem notes
022 a ISSN  
030 a CODEN  
065 a ADS-CODE  
  2   "ADS"
130 a journal-title  
  b short-title not standard
530 a   name of related jnl
  0   recid of related jnl
  w   type of relation (a predecessor, b successor, r otherwise related
  i   specify relation if $$w"r"
540 a   OA tag, license
583 a Harvesting coverage: take "full" journal like JHEP or only "partial" like PRL  
  i Method of harvesting: "feed" by publisher, "harvest" by webscrapping, "print" based on printed journal like Nature  
  c Date of last action on this journal (even if without uploads to HEP)  
  3 volume (issue) of last action  
  x Note  
640 a PDG-ABBREV volume/publication info
643 a   publisher place (needed?)
  b publisher  
667 a NOTE/PPA-NOTE nonpublic note
677 a internal handling e.g. complete coverage
  d doi prefix  
678 a   historical data
680 i   public note
690 a SCL peer review tag
711 a journal short tile not correct marc field
  b letter  
730 a DESYABBREV name variants
  b letter  
8564 u url  
  ? urlnote journal letter
980 a BookSeries  


Are these spires fields needed?

  • PPA-abbreviation
  • oldtitle
  • oldshortti
  • oldcoden
  • tag (Complete, Top100)

DESYABBREV contains all kinds of title variants, some quite strange looking. Which are really needed?

Do we need separate fields for NOTE and PPA-NOTE (example: DESY checks completely). We could define a separate field for coverage (e.g. complete, selected, not checked).

Do we want a field for source of article metadata? (oai, ftp...)

What's the difference between short-title and ppa-abbreviation?

-- AnnetteHoltkamp - 03-Jul-2012 -- AnnetteHoltkamp - 20-Dec-2012

Edit | Attach | Watch | Print version | History: r16 < r15 < r14 < r13 < r12 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r16 - 2017-08-14 - AnnetteHoltkamp
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Inspire All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback