aboutsummaryrefslogtreecommitdiffstats
path: root/guide
diff options
context:
space:
mode:
Diffstat (limited to 'guide')
-rw-r--r--guide/src/roadmap.md36
1 files changed, 35 insertions, 1 deletions
diff --git a/guide/src/roadmap.md b/guide/src/roadmap.md
index c4cc6a98..47e30192 100644
--- a/guide/src/roadmap.md
+++ b/guide/src/roadmap.md
@@ -4,6 +4,10 @@ Core unimplemented features (as of February 2019) include:
- rate-limiting and spam/abuse mitigation
- actual entity creation, editing, deleting through the web interface
+- several web interface views (eg, editor-specific changelog, recent changes)
+- "work aggolomeration", merging related releases under the same work
+- linking known citations (we know DOI or PMID of "target", but haven't updated
+ reference to point to fatcat ident)
Contributions would be helpful to implement:
@@ -16,18 +20,48 @@ Contributions would be helpful to implement:
- internationalization of the web interface (translation to multiple languages)
- accessibility review of user interface
-Longer term projects could include:
+Possible breaking API and schema changes:
+
+- move all edit endpoints under `/editgroup/<editgroup_id>/...`, instead of
+ having an `editgroup_id` query parameter
+- rename `release_status` to `release_stage`
+- handle retractions/withdrawls with `widthdrawn` and `withdrawn_date` release
+ fields, and `retracted` status
+- new entity type for research institutions, to track author affiliation. Use
+ the new (2019) ROR identifier/registry
+- container nesting, or some method to handle conferences (event vs. series)
+ and other "series" or "group" containers
+- include more author name metadata (display, sur, given) in contribs, and
+ potentially references. Need this to format citations properly (CSL) when we
+ don't have full author linkage
+
+Other longer term projects could include:
- full-text search over release files
- bi-directional synchronization with other user-editable catalogs, such as
Wikidata
- alternate/enhanced backend to store full edit history without overloading
traditional relational database
+- make external identifiers generic, instead of having a fixed (indexed) list.
+ Eg, extid table for every entity rev, with string ("issn:1234-5678") or
+ structure ('{type: "issn", value: "1234-5678"}')
+- URLs for entities. Have avoided so far, in lieu of external identifiers or
+ web captures
+- "save paper now" feature in web interface
+- generic tagging of entities. Needs design/scoping; a separate service?
+ editor-specific? tag by slugs, free-form text, or wikidata entities?
+ "delicious for papers"?. Something as an alternative to traditional
+ hierarchal categorization.
+- first-class support for books: additional external identifiers, metadata
+ tweaks, bulk import of MARC or other metadata records, matching to DOAB and
+ other open-access book collections
## Known Issues
- changelog index may have gaps due to PostgreSQL sequence and transaction
roll-back behavior
+- search is idiosyncratic: does not cover contrib names by default, and some
+ queries cause errors (eg, "N/A" without quotes)
## Unresolved Questions