Child pages
  • 2017-2019 EZID & N2T Roadmap
Skip to end of metadata
Go to start of metadata

Link to roadmap planning Gdoc

Comments from Greg in red

User Interface (UI) Improvements

  1. Add support for suffix pass-through for ARKs (done in the sense that we chose an alternative approach)

Application Programming Interface (API) Improvements

  1. Add a rule-based batch processing facility to EZID (done); implement using JSON:API with an eye towards eventually supporting JSON across the entire EZID API (there was just one client who asked for JSON, years ago; if we were to do it all over today, would probably use JSON; is that enough reason to add JSON support now?)

  2. Add support for public ARK identifiers having metadata to enhance their discovery. (on our other roadmap already)
  3. Add EZID support for suffix pass-through. (done)

  4. Implement OAI-PMH for n2t. (not clear how this could be done, for the same reason it's difficult to have N2T return JSON-LD metadata: N2T doesn't know how to interpret the metadata it is storing, and OAI-PMH requires mapping to common citation metadata standard(s))

  5. Release new Compact Identifier service. (we have a service, what is meant by "new"?)

Architecture Improvements

  1. Complete implementation of N2T’s and EZID’s high availability (HA) server architecture for reliability and redundancy. (for EZID, tabled due to too little bang for buck)

Community and outreach objectives

  1. Support clients' transitions to other DOI providers. (done/doing)
  2. Work with partners to explore support for hard identifier-related problems, such as long lists of authors, contributors, etc., or multiple destinations for resolution, by engaging in community discussions, collaborating in projects, and presenting at workshops and conferences. (there are worthy problems here (aliasing, PID usage) but not sure we're engaged with the right communities to tackle these)
  3. Conduct a pilot project to implement and test metadata to convey persistence commitments between providers and users. (would be interesting)
  4. Support persistently-identified metadata vocabulary terms by
    1. hosting the crowd-sourced tool and
    2. building a community of contributors and developers.
  • No labels