You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

The arXiv roadmap is a living document and communication tool 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 opportunities and initiatives as they arise, and progress on next generation arXiv development.

Beginning with this roadmap (2018) we are treating arXiv-NG and "classic" arXiv development, business planning and governance as a single, unified effort. For technical development, some parts of arXiv will be rebuilt anew, while others will be transitioned in stages (utilizing "shims") to new infrastructure.

Much of the work planned for 2018 is essential infrastructure that is required in order to rebuild arXiv. Many tasks involve dependencies and cannot be reprioritized if the overall effort is to move forward.

Technical 

Switch over to New Database Infrastructure: This is a system operations priority. 

  Status: Completed January 2018.

Author Notification of Reclassification:  Add new features to provide authors with notification about reclassification of their paper.  Notifications will provide information about follow-up action that is required (i.e., what action in what timeframe). 

  Status: Initial specification in progress; pending policy input

Auto-endorsement: Shift the auto-endorsement rules to work of a single white-list of recognized email domains. Expand the list of email domains that qualify for auto-endorsement. Develop an admin interface to update the auto-endorsement list.

  Status: White list complete; implementation not started. 

Infrastructure: New infrastructure setup and configuration to support deployment of arXiv-NG services in the cloud.

  • Centralized Logging Infrastructure:  classic and NG systems deposit access and application logs in a centralized log store. Status: In progress.
  • Cloud Deployment Infrastructure:  implementation of service deployment and networking infrastructure. Status:  In progress.
  • Backup & Recovery finalization of backup and recovery strategy for NG.

Submission System: Implements user interfaces and APIs for submissions in the NG architecture.

  • Essential utility services: isolating essential processes from the classic system. Includes fulltext extraction, classifier, overlap detection, upload sanitization, TeX/compilation service, etc. This lays the  foundation for isolating the submission system as a whole from the legacy codebase.  Status:  In progress.
  • Submission shim:  the submission UI is replaced with a Flask application that runs on the existing CUL web servers. Includes allowing users to view and rewrite notices of self-overlap prior to publish.
  • User experience and file transformation: improvements to user experience in the submission system, especially related to TeX compilation.
  • Submission API:  a new interface to support programmatic submission of papers. This is part of the broader automated submission collaboration with partner organizations. May involve implementation of forthcoming version 3 of the SWORD protocol. Will replace the SWORDv1 API.

Accounts & Authorization: Implements mechanisms for user registration, authentication, and authorization in the NG architecture.

  • Login & distributed sessions:  authentication views  are handled by a new accounts service running on CUL servers, integrated with a distributed session store. This makes it possible to deploy new services with protected views in the cloud.
  • Authorization service: implementation of a service for managing user and API client authorizations in NG services.
  • Registration & profile management:  accounts service is extended to replace account registration views, including password reset.
  • OAuth2 support:  accounts service supports OAuth2, which allows arXiv users to authorize API clients to perform actions on their behalf. Necessary for submission API.

Enhancement & Discovery: Browse: Redeveloping abstract page and subject listing display (home page). Initial focus on abstract pages; to be implemented in Python/Flask.

  • Abstract page: a new Flask application running on the existing CUL web servers replaces the abs view, with minimal design changes. This facilitates decoupling elements of display from the classic system. Status: In progress.
  • ORCID links: expose ORCID information that we already have (~34,000 ORCID identifiers in the classic system) on the abstract page.
  • Display external links: author-contributed external links provided by external links service are displayed on the abs page.
  • Additional browse views:  classification views (/archive, /list, /year) are provided by the browse application.

APIs & API Gateway: Provides an integrated access point for programmatic consumption of arXiv content. 

  • Public API gateway: a public API gateway is available. arXiv users are able to register their application and receive an API token, which is used to access API resources. At this stage, we will expose search API, fulltext content, and automatically extracted cited references. Status:  In progress.
  • RSS feed:  RSS feed is reimplemented as a standalone service, available via the API gateway. Deprecates the classic RSS feed.

Enhancement & Discovery: Search:  Combined metadata and full-text search using Elasticsearch and Python/Flask as a standalone application.

  • Replace legacy search:  reimplementation of the existing search views (/find), including advanced search functionality, in a new search service backed by Elasticsearch.Status:  In progress.
  • REST API: provides a search-backed RESTful JSON API for arXiv papers via the API gateway. Deprecates the classic XML-based arXiv API.
  • Classic authority/ORCID views: search application has new views that replace the authority record (https://arxiv.org/a/warner_s_1.html) and ORCID (https://arxiv.org/a/0000-0002-7970-7855.html) views in the classic system. Integrated with the author name authority service.
  • Faceted search: the search interface is extended with facets, providing the ability to refine search results based on metadata. 
  • Full text search:  support for full-text search is well documented, and improvements are made to the UI to give users’ visibility and control over this functionality. 

Publication & Preservation: Services to support the publication process and core metadata to ensure that arXiv papers and metadata are protected from loss, and that they remain uncorrupted and accessible.

  • Author name authority service: transforms the existing name authority mechanism into a more robust name authority service that provides URIs for unique author identities, supports mappings between author identities and external identifiers (e.g. ORCID), and provides mechanisms for mapping duplicate entries onto each other.
  • Institution authority records: name authority service is extended to support an institution record type, and back-filled with affiliation information already present in the classic database.
  • Email notifications:  authenticated users can configure their e-mail subscriptions in an announcement service.

Enhancement & Discovery: Metadata: Backend support for peripheral metadata, including relations to external resources (e.g. journal articles, datasets, code, etc).

  • External links service: implements a backend service for storing and serving secondary relational metadata about arXiv papers, with provenance. Will support author-curated links, and eventually assume responsibility for DOI and JREF metadata.

Reference Linking: Pilot project to display linked references to users.

  Status:  In progress (see blog entry)


Public code respositores: Provide access to open source components of arXiv codebase as they become available. List of arXiv's public repositories

NB: approximately 20% of developer effort is devoted to a range of activities that ensure that the service continues to run smoothly; this effort is variable from week to week and is not necessarily scheduled or reflected by discrete tickets in our task management system. Activities include (but are not limited to) the following:

  • server maintenance and troubleshooting
  • service monitoring
  • analytics
  • internal support requests
  • ad hoc meetings and conferences
Given the relatively small size of the development team, which does not currently have a dedicated dev/ops engineer, every team member is responsible for some amount of operational work. 

User Support

Publish Physics Category Descriptions:  Finalize input from moderators and publish the descriptions on arXiv.org. 

Status:  In progress; awaiting review.

Help Page Updates: Ongoing project to update arXiv help pages.

Status:  Ongoing. Migration of pages to new repository planned for summer 2018

Refine User Account Policies: Update internal documentation on user account policies and identify ways to automate actions.

Status:  In progress.

Moderation

Position Descriptions for Volunteer Roles: Develop position descriptions for various arXiv volunteer roles to be used in recruitment. 

Reorganize Moderator Guides: Update moderator documentation. Reorganize the expanded guidelines for moderators. 

Business Model & Governance

Society-arXiv Collaboration: Consider adding a new membership category for societies to support arXiv and contribute to its governance. A preliminary proposal will be drafted by an MAB/SAB subgroup to be discussed by the advisory boards.

arXiv Governance and Business Model Assessment: As arXiv is going through a classic renewal process to modernize the architecture, continue to explore the current business and governance model's effectiveness and durability to ensure that arXiv is stewarded to the future in a successful manner.

Special Projects (under consideration)

A number of special projects from previous roadmaps are being incorporated into next generation arXiv planning and development.

The current 5-year business plan represents a baseline maintenance scenario. It was developed based on an analysis of arXiv's baseline expenses during 2010-2012. It does not factor in any new functionality requirements or other unforeseen resource needs. Although a development reserve was established to fund such expenses, it is not sufficient to subsidize significant development efforts through surplus funds. 

Supporting public access mandates: The arXiv public access subgroup has been formed to explore the feasibility and desirability of expanding arXiv's features to support the public access requirements of research funders, and institutions' ability to monitor the compliance of their researchers. The subgroup’s input will be crucial as we seek to understand if and how supporting those requirements might align with arXiv's existing goals and priorities.

Videos for Moderator Training: Improve the moderator training experience with short videos on using the moderator tools and dealing with common scenarios.

Preprint Service Providers Summit: Collaborate with ASAPbio and bioRxiv to bring together the nascent preprint service providers from several different disciplines to discuss a range of curation and maintenance issues of common interest and to foster information sharing and standard practices. 

  • No labels