Plan the MVP dataset issue tracker

[robyngit]

Design the first iteration of a dataset-level issue tracker. The issue tracker will serve as a central platform for collaboration between data authors and curators. This will not only improve the quality of the dataset but also speed up the publication process.

The issue tracker should enable discussion of curation issues and would track resolution as subsequent versions of the dataset are produced. It should allow for private, internal discussion when the data are private, and should integrate seamlessly into a new workflow for curation and submission of data for publication.

This issue involves assessing key features of the MVP and the steps involved in implementing them. We may want to evaluate existing issue tracking solutions that we could integrate into MetacatUI.

[robyngit]

Backend service options

• Can use github api
• Previously used annotation docs in metacat, but complex with pid/versioning system. Used perl.

[robyngit]

Notes from discussion on this:

• Use RT, which is already in use and has an API
• expose the RT discussion threads in MetacatUI
• Add ability to add a comment via an RT thread
• May need to use a proxy to avoid exposing RT credentials
• This first iteration will be pretty ADC specific
• Create a model for discussions and populate it from different services, through RT at first, but later other services
• If a user is logged in with write permission on a dataset, then can view RT thread
• arctic bot uses RT API - reference this