PROJECT DIRECTOR | Oya Rieger |
PROJECT COORDINATOR | Gail Steinhart |
START DATE | 12/1/2016 |
END DATE | 6/30/2018 |
APPROVED BY | arXiv-NG Steering Committee: Oya Rieger, Sandy Payette, Gail Steinhart, Martin Köhler (MAB), Dave Morrison (SAB) |
APPROVAL DATE | 3/21/2017 |
APPROVED VERSION | 1 |
CURRENT VERSION | 1 |
LAST UPDATED | 2/7/2017 |
arXiv is an openly accessible, moderated repository for scholarly articles in specific scientific disciplines. arXiv provides rapid and perpetual access to content, without any fees and with support for users around the world.
...
Oya Rieger, arXiv Program Director and Principal Investigator, has overall responsibility for this project and is responsible for business planning efforts. The arXiv-NG Steering Committee has decision-making authority. More complete information on roles and responsibilities is summarized below.
arXiv-NG groups and teams | Roles and responsibilities |
Program Director and Principal Investigator: |
|
|
Steering group members: |
|
|
|
|
|
|
|
arXiv-NG Operations team: |
|
|
|
|
|
|
arXiv-NG IT advisory group: |
|
|
|
|
|
|
|
|
|
Gerald Beasley, Cornell University Librarian |
|
Additional stakeholder groups
...
RESOURCE REQUIREMENTS
Staff resources
TEAM ROLE | NAME | SUPPORT |
Project Director | Oya Rieger | CUL supported |
Project Coordinator | Gail Steinhart | Grant & CUL supported |
CTO | Sandy Payette | CUL supported |
arXiv lead developer | Martin Lessmeister | Grant supported |
Lead system architect | Vacant | Grant supported |
Developer | Vacant | Grant supported |
Operations Manager | Jim Entwood | CUL supported |
Scientific Director | Vacant | CUL supported |
RISKS AND CONSTRAINTS
A separate risk analysis will be conducted.
...
It is our intention to continue uninterrupted operation of the current arXiv system, and essential, modest improvements will continue to be made. We have yet to decide whether our rebuild strategy will be to a) isolate components of the current (“classic”) arXiv system, build new equivalents, and carefully integrate the new components into the existing system, or b) build an entirely new system and migrate content in the classic system to the new one upon completion and successful testing. An approximate timeline for the concurrent maintenance of the classic system and development of arXiv-NG follows. The uncertainty (?s) indicated in the timeline has to do with the choice of the a) or b) scenario - a) implies continuous operation of the classic system while improvements are made to it, while b) implies a shut-off and migration date.
WORK ITEM | PROJECT PERIOD* | |||||||||||
Phase I | Phase II | |||||||||||
1 | 2 | 3 | 4 | 5 | 6 | 1 | 2 | 3 | 4 | 5 | 6 | |
arXiv classic | ||||||||||||
Modest enhancements (see roadmap) | X | X | X | X | X | X | X | X | ? | ? | ||
Maintain current arXiv production service | X | X | X | X | X | X | X | X | X | X | ? | ? |
arXiv NG | ||||||||||||
Project charter | X | |||||||||||
Communication plan | X | |||||||||||
Technical requirements and principles | X | |||||||||||
Workflow diagrams and mapping | X | |||||||||||
Technology evaluation | X | X | ||||||||||
Partnership evaluation | X | X | ||||||||||
Selection of framework and technology | X | |||||||||||
Technical architecture - design, diagrams, APIs | X | |||||||||||
Comprehensive transition plan | X | |||||||||||
Draft business and governance models | X | X | X | |||||||||
Grant proposal(s) for Phase II | X | X | ||||||||||
Usability testing plan | X | |||||||||||
APIs/UIs/prototypes for submission, moderation, access | X | X | X | |||||||||
APIs/stubs for core modules - storage, db, registries, index | X | X | ||||||||||
APIs/integration tests for search, TeX, other services | X | X | ||||||||||
User testing | X | X | X | X | X | X | ||||||
Iterative development I | X | X | X | X | X | |||||||
Iterative development II | X | X | ||||||||||
Iterative development III | X | X | ||||||||||
Complete transition | X | X |
* Each project period represents three months.
...