Versions Compared

Old Version 1

changes.mady.by.user user-92500

Saved on

compared with

New Version 2

changes.mady.by.user user-92500

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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:

 Oya
  • Oya Rieger

  • Has overall responsibility for project.

  • Leads business planning efforts.

  • Has final decision making authority in consultation with the Steering Group (shared responsibility with Scientific Director, currently vacant.

Steering group members:

 Oya
  • Oya Rieger, PI
 Sandy
  • Sandy Payette, CTO
 Gail
  • Gail Steinhart, Project coordinator
 Scientific
  • Scientific Director (vacant)
 Dave
  • Dave Morrison, SAB
 Martin
  • Martin Köhler, MAB

 

  • Provides strategic advice to PI especially in regard to decision-making on high-level issues.

  • Counsels on reconciling different stakeholder perspectives.

  • Contributes to developing communication strategies with various stakeholders.

  • Represents interests of relevant stakeholder groups.

arXiv-NG Operations team:

 Sandy
  • Sandy Payette, CTO
 Martin
  • Martin Lessmeister, Lead developer
 Gail
  • Gail Steinhart, Project coordinator
 Jim
  • Jim Entwood, Operations Manager
 arXiv
  • arXiv-NG developers

 

  • Implements and carries out project.

  • Forms appropriate partnerships.

  • Takes direction from and communicates regularly with arXiv-NG steering group.

  • Communicates regularly with the current arXiv operations and IT teams, fostering understanding, support and application of arXiv-NG’s “first principles.”

  • With other teams, seeks additional funding for next phase.

  • Identifies and relays problems, impediments, risks in a timely manner to PI and SG.

arXiv-NG IT advisory group:

 Alberto
  • Alberto Accomazzi, NASA ADS
 Paul
  • Paul Ginsparg, Cornell, arXiv founder
 Robert
  • Robert Hanisch, NIST
 Dave
  • Dave Lifka, Cornell University CIO
 Mark
  • Mark Matienzo,
DPLA
  • Stanford University Library
 Matthew
  • Matthew McGrattan, Digirati
 Thorsten
  • Thorsten Schwander, SLAC/INSPIRE

  • Provides input on technology and partnership choices.

Gerald Beasley, Cornell University Librarian

  • Has overall responsibility for arXiv’s obligations.

  • Provides institutional support and resources for arXiv (HR, business services, legal, etc.).

  • Is final arbiter for arXiv and arXiv-NG decisions.

 

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.

...