...
- Centralized Logging Infrastructure: classic and NG systems deposit access and application logs in a centralized log store.
Status: In progressBeta.
- Cloud Deployment Infrastructure: implementation of service deployment and networking infrastructure.
Status: Initial infrastructure in place with some production componentsBeta.
- Backup & Recovery finalization of backup and recovery strategy for NG.
...
Submission System: Implements user interfaces and APIs for submissions in the NG architecture.
- Submission UI: 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.
Status: Alpha.
- 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.
...
:
...
Status: In progress.
- User experience and file transformation: improvements to user experience in the submission system, especially related to TeX compilation.
Status: In progress.
- 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.
...
- 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.
Status: Complete.
- Authorization Authentication service: implementation of a service for managing user and API client authorizations authentication in NG services.
Status: In progressAlpha.
- 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.
Status: Not startedAlpha.
Enhancement Access & 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 (~50,000 ORCID identifiers in the classic system) on the abstract page.
Status: Not started.
- Display external links: author-contributed external links provided by external links service are displayed on the abs page.
Status: Not started.
Beta.
- Additional browse views: classification views (/archive, /list, /year) are provided by the browse application.
...
- 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 Alpha.
- RSS feed: RSS feed is reimplemented as a standalone service, available via the API gateway. Deprecates the classic RSS feed.
Status: Not started.
Enhancement Access & Discovery: Search: Combined metadata and full-text search using Elasticsearch and Python/Flask as a standalone application.
...
- REST API: provides a search-backed RESTful JSON API for arXiv papers via the API gateway.
Status: Not started Alpha.
- 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.
...