Thinking about how to port Authority Files (like Institutions/Conferences/HepNames) into Inspire

List of Existing SPIRES Files

  • Institutions standard inst. names, supplemented with address info, country, contact info, tagging
  • Conferences standard conf names, suppl with urls (info and proceedings), dates, location
  • Experiments standard expt names, suppl with author lists (poorly maintained), lab information, keywords, dates (badly maintained)
  • HEPNames not used to standardize - but lists institutional history, contact info, web pages, family tree (students/advisors)


We may need different plans for each file, but I see 2 primary options

  • Migrate into invenio structure, either within MARC formalism or in custom MySQL tables
  • Keep in SPIRES files and use http requests for verification functions within invenio
    • In this case we may eventually migrate to a MySql file, but inspire wouldn't need this migration to be completed before being functional...

I like the seond option best, because it frees up development time, and we don't have to do all the mapping at once. However if the authority mode available in invenio is expecting to find things within invenio, then we might have to think again.

-- TravisBrooks - 02 Jul 2007

Additional Files outside SPIRES

  • DESY keywords + list of keyword abbreviations (used by inputters)
  • standardized report nrs (coupled with resp institution)
    • Should we maintain this list? It is useful for sorting and checking report series for completeness. The link to the corresponding institute could be helpful for non-unique report series or to create reference lists for annual reports. But I'm not sure whether it's worth the effort.

-- AnnetteHoltkamp - 11 Jul 2007

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2008-02-05 - TiborSimko
    • 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