Date: Fri, 29 Mar 2024 06:49:25 -0500 (CDT) Message-ID: <1330888787.4165.1711712965507@cornell1-cos-conf1.managed.contegix.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4164_79989006.1711712965507" ------=_Part_4164_79989006.1711712965507 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The arXiv roadmap is a living document and communication too= l to accommodate continuous prioritization throughout the year. Items = are listed in approximate priority order, subject to change based upon= consideration of input from arXiv stakeholders, assessment of new opportun= ities and initiatives as they arise, and progress on next generation arXiv = development.
Moderator Web UI: Implement enhancements to the e= xisting moderation Web UI to improve the proposal system based on moderator= feedback. Also, enable moderators to take multiple actions and commi= t them together as a set of actions. Develop a new alternate moderator= user experience to offer an efficient way for moderators to work on multip= le submissions on a single responsive web page. The alternate moderator use= r experience will provide new paradigm for category management, improved pr= oposal features, and an improved notification scheme to decrease email volu= me for moderators.
Status: Initial release June 2017; with subsequent mino= r improvements.
Moderation API: Define and implement a new API th= at provides a service endpoint for all essential operations necessary to su= pport the moderation workflow. The API will be brought forward in to the ne= w arXiv-NG architecture with the intention of it being able to support new = applications and user interfaces in the future to support moderation in arX= iv-NG.
Status: Completed.
Upgrade database infrastructure: This is a system opera= tions priority.
Status: provisioning and initial configuration complete= d. Final configuration and tuning in progress with planned switchover in ea= rly 2018.
PHP/tapir to PERL/Catalyst: Complete the conversi= on of PHP code to provide modularity, consistency, and improved maintainabi= lity of key parts of arXiv codebase. Migrate functions away from old PHP/Ta= pir codebase and into Perl/Catalyst.
Status: Retired to reallocate effort towards reimp= lementing as Python/Flask application.
Improve submission error checking: Analyze submiss= ion process to identify improvements and minimize submission errors for aut= hors.
Status: Analysis of existing system complete; re-i= mplementation of submission in Python/Flask is in progress. Scope work for = improving error handling and display not started.
Author notification of reclassification: Add new = features to provide authors with notification about reclassification of the= ir paper. Notifications will provide information about follow-up acti= on that is required (i.e., what action in what timeframe).
Status: Initial specification in progress; implementation = deferred to 2018 pending final policy decisions.
Auto-endorsement: Shift the auto-endorsement rules to w= ork of a single white-list of recognized email domains. Expand the list of = email domains that qualify for auto-endorsement. Develop an admin inte= rface to update the auto-endorsement list.
Status: White list complete; implementation not started= .
Submission system security audit: This is a system= s operations priority.
Status: Completed for current codebase.
EESS: (Electrical Engineering and Systems Science) doma= in expansion
Status: Complete. Launched with 3 subcategories on 18 S= ept 2017.
Econ: (Economics) domain expansion
Status: Complete. Launched with one subcategory on 26 S= ept 2017.
Reference extraction: (promoted from Special Proje= cts) Automatically extract references from papers.
Status: Implemented. Extraction for all new papers.&nbs= p; (see blog entry)
Reference linking: (promoted from Special Projects= ): Display linked references to users.
Status: API for reference links implemented. Disp= lay implementation deferred, pending consideration of user feedback and Sci= entific Director input. (see blog entry )
Search: (promoted from Special Projects):&= nbsp;Combined metadata and full-text search using ElasticSearch an= d Python/Flask as a standalone application.
Status: In progress.
Browse: Redeveloping abstract pag= e and subject listing display (home page). Initial focus on abstract p= ages; to be implemented in Python/Flask.
Status: In progress.
Log Analysis: Redevelop general l= og analysis code, including annual institutional usage statistics; to be im= plemented in Python and AWS.
Status: Introduced late 2017; in progress.
Submission API: ACM submission special project evolved = into multi-stakeholder initiative to design a new submission API in NG.
Status: Introduced late 2017; in pro= gress.
NB: approximately 20% of developer effort is devoted to= a range of activities that ensure that the service continues to run smooth= ly; this effort is variable from week to week and is not necessarily schedu= led or reflected by discrete tickets in our task management system. Activit= ies include (but are not limited to) the following:
Author curated links: Based on the findings of the= arXiv user study , improving support for linking= research data, code, slides and other materials associated with papers eme= rged as an important service to expand.
Status: Not started; to be implemented in Python/F= lask.
Publish physics category descriptions: <= /strong>Finalize input from moderators and publish the descriptions on arXiv.org= . This work started in 2016 and we hope to complete early 2017.&nb= sp;
Status: In progress; awaiting review.
Overlap policy: Implement the SAB Sept 2014 decision th= at cases of self-overlap get bounced to users before publishing.
Status: Not started. Dependent on submission and o= verlap tools currently in development.
Update Help pages: Assess which section of the Hel= p pages to update in 2017 (submission, moderation, reading/downloading, etc= ). Rewrite those sections. Identify straggling pages and pages that could b= e slated for removal.
Status: Completed for 2017.
Systematize arXiv's individual archive pages: The = "home" pages for individual archives within arXiv have grown organically ov= er time and are inconsistent with each other and in some cases outdated.&nb= sp;
Status: Deferred for more systematic site map revi= ew and development process.
Stakeholder communication improvements:
Status: Implemented quarterly Roadmap and backlog = reviews.
Develop and implement s takeholder engagement p= lan:
Status: Implemented quarterly stakeholder reports;= revamped arXig blog and distributed quarterly blog digests; established tw= itter account.
Develop and implement use r engagement plan:
Status: Implemented arxiv-usability-l email list t= o announce polls/surveys and solicit subjects for usability testing. Conduc= ted two surveys to inform design decisions. Developed protocol for remote u= sability testing and applied to development of new moderation interface.
Continuous prioritization of development priorities:&nb= sp;
Status: Implemented.
Status: Implemented with the development of the 2= 017 Roadmap.
arXiv Workflow and Moderation analysis: Embark on = a fresh analysis of workflows for moderators, appellate moderators, an= d Chairs. Identify and implement process improvements. This will info= rm both classic arXiv and arXiv-NG. Improve communication to moderator= s regarding system updates, process improvement, guidelines for moderation,= and recruitment. Expand documentation on roles, relationships, and wo= rkflows between moderators, appellate moderators, committees, and Chairs.= p>
Status: Expanded internal documentation for modera= tors regarding specific policies. Integrated classifier tool into the propo= sal system. Conducted design sessions around workflows and interfaces to in= form future improvements.
Recruit a Scientific Director: In 2014, we created the = Scientific Director position to provide intellectual leadership for arXiv a= nd appointed Dr. Chris Myers as the interim Scientific Director to test and= refine the role. After Chris Myers's departure in April 2016, we have star= ted to revise the job description with the goal of filling the position in = 2017. The Scientific Director (.5 FTE) will collaborate with the arXiv staf= f and the arXiv's Scientific Advisory Board in providing intellectual leade= rship for arXiv's operations.
Status: Completed. After Chris Myers=E2=80= =99 departure in April 2016 as the interim Scientific Director, we took a f= ew months to review the original job description and expectations and Chris= =E2=80=99s assessment of how the position played out in reality. Accordingl= y, a revised job description was develope= d and and announced. We are pleased to announce that Professor Steinn Sigur= dsson accepted the position and will start in September, working remotely f= rom Penn State. Coordinated by Oya Rieger, the search committee included Da= ve Morrison (SAB), Carol Hoover (MAB/SAB liaison), and Eberhard Bodenchatz.=
Continue the membership drive & identify new funding sources= : Ensuring a broad international network of supporters requires an= ongoing effort in order to develop new outreach strategies and revenue sou= rces. We will continue our efforts in increasing awareness about sustainabi= lity issues and the arXiv business plan. Also, we will raise additional rev= enue streams through online fund raising campaigns and the promotion of the= new sponsorship program.
Status: In progress with successful online fund raising= efforts.
Create a business model for 2018-2022: This is the fina= l year of our 5-year business plan. We have started planning for t= he next 5-years during 2016 and will finalize and announce the new model, i= ncluding a revised tier structure.
Status: The new business model was finalized and rolled= out in Spring 2017: 2018-2022: Sustainability Plan for Classic = arXiv
Raise funds to support arXiv-NG project: In addition to= raising funds to support the current arXiv operation, during 2016, we succ= essfully secured two grants in the amount of $650,000 to initiate the next-= generation arXiv initiative, which is envisioned to be a 3-year project wit= h a total budget of $2+ million. Therefore it is essential that we continue= writing grants to raise the necessary funds for successful and timely comp= letion of the project. Click for more information on arXiv-NG initiat= ive.
Status: In progress - proposal submitted to Heising-Sim= ons Foundation
Based on the conclusions of ten months of planning activities during 201= 6, the arXiv team successfully secured a $450,000 grant from th= e Sloan Foundation to initiate the next-generation arXiv (arXiv-NG= ) initiative. The 18-month project will enable us to plan and begin t= o improve the architecture of this critical scientific infrastructure. We a= nticipate that a multi-phase design and development of a next-generation ar= Xiv (arXiv-NG) will require approximately 3 years with an additional $2+ mi= llion budget, including requirements specification, evaluation of alternate= strategies and partnerships, design of a new system architecture, assessme= nt, and deployment. As we are developing arXiv-NG, during the next three ye= ars we will continue to rely on the existing system (Classic arXiv) and are= committed to continue its robust services. Additional information:&nb= sp;Next Generation arXiv
Another source of funding in support of arXiv-NG came from the Allen = Institute for Artificial Intelligence (AI2). An initial gift of $2= 00,000 for 2017 will support a collaboration between the Cornell University= Library and the Cornell Computing and Information Science (CIS). Thi= s donation will allow us to hire a Research & Innovation Fellow to coll= aborate with the arXiv team in designing and integrating a series of update= d, research-oriented features for arXiv. The ultimate goal is to integrate = tools that emerge from research into the production system to improve user = and moderator experience.
A number of special projects from previous roadmaps are being incorporat= ed into next generation arXiv planning and development.
The current 5-year business plan represents a baseline maintenance scena= rio. It was developed based on an analysis of arXiv's baseline expenses dur= ing 2010-2012. It does not factor in any new functionality requirements or = other unforeseen resource needs. Although a development reserve was establi= shed to fund such expenses, it is not sufficient to subsidize significant d= evelopment efforts through surplus funds.
ACM preprint loading into arXIv and submission API collaboration=
Selected interoperability initiatives
Improve ORCID integration
Other initiatives