DataONE API version 2 needs to be supported
This is an overarching story for v2 of the DataONE Service API. After many planning meetings, we decided to pursue a v2 design that supports versionable content using a seriesId field in the system metadata for each object. Likewise, API changes in v2 will support Member Node management of system metadata in the federation, as opposed to Coordinating Node management (which is the current state). For background on decisions, see the latest "design document":https://docs.google.com/a/nceas.ucsb.edu/document/d/1uK4WqoMuMqM93J03Z2N1Hm2-IkgZe4kXMNlieSjS-SY/edit , which will be moved into the DataONE documents repository.
The implementation involves changes to the DataONE Types Schema, the low level libraries (d1_common_java and d1_common_python) that express the API changes, and each software component in the Coordinating Node stack and various Member Node stacks.