igsn:11_july_2012_wednesday_telecon

This is an old revision of the document!


Table of Contents

IGSN e.V. Telecon July, 11, 2012

10:00am EDT, GoToMeeting

Agenda

  1. status of registration of IGSN eV
    1. registration is in progress, the papers are at the court.
  2. IGSN syntax
    1. recent emails summary: IGSN syntax is still open. It looks to me like we need a hybrid system of 9-character (non-mnemonic) and longer (mnemonic) names.
    2. Elsevier linking proposal - we need to confirm: Elsevier can resolve the following syntax ‘IGSN: (space) number’. Even if authors don’t put in the space, Elsevier should be able to pick up this variation
  3. Registration agents & their relation to the SESAR metadata clearinghouse
  4. Metadata schemas? (what has happened in the working group?)
    1. IGSN metadata schema ready to be finalised
    2. IGSN registration web service ready once the schema is finalised.
    3. SESAR metadata schema is final (?)
  5. Upcoming IGC workshop and how to deal with potential membership applications
  6. AGU Session on Unique Identifiers - who to invite?
  7. Any more comments on brochure content (yes, still working on design aspect), send to lhsu@ldeo.columbia.edu
    1. Instead of ““IGSN e.V. is not a standard metadata scheme.””, IGSN defines a minimal schema to *register* the sample, but not a complete schemato *describe* the sample. Also, see wiki updates.
  8. New membership applications:
    1. any potential new members at IGC wil just make it to go through the formal processes before the AGU Fall Meeting. This means, we could discuss new applications at the AGM in San Francisco.
  9. Status of SESAR interface development?

Notes

  1. Discussion about syntax:
  2. Metadata Clearinghouse
    1. Discussion of whether this be mandatory or optional
    2. To follow the DataCite model, for an IGSN to be assigned the core set of metadata must be deposited at a clearinghouse.
  3. Metadata Schema
    1. We should move ahead and if changed are needed in the future then there can be amendments.

Actions

  1. Document the recommended practice for the syntax, and the procedure to deviate
  2. Document the proposed namespace management
  3. Brochure feedback by July 20th
igsn/11_july_2012_wednesday_telecon.1342018921.txt.gz · Last modified: 2012/07/11 15:02 by lhsu