PART 2: FUNCTIONAL EVALUATION | Candidate 1 | Candidate 2 |
---|
1. Data model | Priority | Rating | Rating |
---|
- Generic (core data model)
| | | |
- Flexible and Extensible (core model can be extended)
| | | |
- Model for key entity types (e.g., publication entities; scholarly objects; research objects)
| | | |
- Supports relationships (e.g. part/whole; reference links; semantic
| | | |
- Supports custom metadata
| | | |
- Supports multiple identifiers (local and global)
| | | |
- Supports aggregation of entities (e.g., via part/whole relationships)
| | | |
- Amenable to serialization in multiple standard formats
| | | |
2. Metadata Store | Priority | Rating | Rating |
---|
- Flexible database schema
| | | |
- b. Ability to store metadata as objects (e.g., json)
| | | |
3. Object Store | Priority | Rating | Rating |
---|
- API is well-defined and documented
| | | |
- Flexible content type (text, binary, data, video, image, PDF, other)
| | | |
- CRUD operations on objects upon objects in persistent storage
| | | |
- Versioning of objects
| | | |
- Backup of objects
| | | |
- Redundancy/replication of objects
| | | |
- Pluggable storage backend (e.g., file system; cloud storage; storage system)
| | | |
- Audit trail of changes
| | | |
- Create checksum of objects
| | | |
- Monitor object integrity (e.g., via checksums)
| | | |
4. Workflows | Priority | Rating | Rating |
---|
- Specification of workflows (outside of code)
| | | |
- Modern, reactive user interfaces for agents of workflows
| | | |
| | | |
| | | |
- Execution and tracking of workflows
| | | |
| | | |
| | | |
- Integration with external services (e.g., call outs)
| | | |
- Classifier, overlap, TeX,
| | | |
- Reference link extraction, metadata extraction
| | | |
| | | |
- User communication and notification
| | | |
| | | |
| | | |
- Event audit trails (also visible via user web pages)
| | | |
- Logging and history (e.g., of submitters and submissions)
| | | |
- RT integration or similar functionality
| | | |
5. Publishing | Priority | Rating | Rating |
---|
- Persistent URLs for arXiv papers
| | | |
- Pre-print DOIs
| | | |
- Changes at specific times: freeze time/ publish time
| | | |
- Move metadata and content to published storage
| | | |
- Triggers for announcements
| | | |
- email announcements to submitters
| | | |
- email announcements of articles
| | | |
6. Discovery and Access | Priority | Rating | Rating |
---|
- Indexing easily configured
| | | |
- Robust search engine (e.g., Elastic; Solr)
| | | |
- Faceted browse
| | | |
7. Services | Priority | Rating | Rating |
---|
- TeX system - Ability to run as external service for processing of submission, moderation, publishing of articles.
| | | |
- Overlap detection
| | | |
- Classification
| | | |
- Reference extraction
| | | |
8. User Interfaces | Priority | Rating | Rating |
---|
- All Web UIs use modern javascript framework
| | | |
- Out-of-box moderation UI
| | | |
- Custom-built moderation workflow UI
| | | |
- Out-of-box submission UI
| | | |
- Custom-built submission workflow UI
| | | |
- Out-of-box browsing UI and preprint page
| | | |
- Custom-built browsing UI and preprint page
| | | |
- Out-of-box administrative UI
| | | |
- Custom-built administrative UI
| | | |
- Faceted search UI
| | | |
9. User account management | Priority | Rating | Rating |
---|
- Integrating existing user account data and history
| | | |
- Flagging user actions
| | | |
- Log in as a user for dev purposes
| | | |
- ORCID integration
| | | |
- Open standards
| | | |
- OAuth2
| | | |
- User action auditing
| | | |
10. Email | Priority | Rating | Rating |
---|
- Sending nightly email
| | | |
- Totally Decoupled
| | | |
- Large scale (~10K daily)
| | | |
- Ability to send one-off emails
| | | |
- emails to specific users
| | | |
- Public relation emails
| | | |
- emails to sets of users (such as those affected by an incident)
| | | |
- Emails to users via user account system
| | | |
- User subscriptions to nightly email categories via email.
| | | |
11. I18N and accessibility | Priority | Rating | Rating |
---|
- Unicode character handling
| | | |
- Should at least not cause problems in this area
| | | |
| | | |
12. CMS or Wiki (for public, admin and policy documentation) | Priority | Rating | Rating |
---|
- Public relation features like front page news posting
| | | |
- RSS feed not tied to records/articles
| | | |
- Help and FAQs pages
| | | |
- Admin policies
| | | |