As an Administrator I want to add textual notes to Datasets and see them in the Dataset Admin UI
11615
Reporter: lfrancke
Type: Story
Summary: As an Administrator I want to add textual notes to Datasets and see them in the Dataset Admin UI
Priority: Minor
Resolution: Fixed
Status: Closed
Created: 2012-07-18 14:45:16.973
Updated: 2017-10-06 15:30:17.097
Resolved: 2017-10-06 15:30:17.083
Description: These little notes should only be visible to administrators.
Implementation ideas:
* New field for all agents
* As a tag]]>
Author: ahahn@gbif.org
Created: 2012-07-19 15:41:54.878
Updated: 2012-07-19 15:41:54.878
As an ... I want to... -> so that I have critical reminders at hand at the point of scheduling resources for indexing.
Examples:
- eBIRD: "2012-07-01, AH: IDs being reconfigured, do not touch until test confirmed" [as the dataset is huge, previous ID changes generate duplicate (wrong) records, so that indexing would make the online status much worse than before without quick reversal option]
- Field Museum: "2012-05-04, JL: verify correct indexing of new setup, then delete this one" [as configuration tests for a migration can sometimes run for weeks, and we do neither want to have the old disappear before the new is ready, nor forget to delete and end up with two copies]
- SomeOBISDataset: "2008-02-15, AH: crawling deactivated because duplicate of set indexed through MNHN" [this duplicate will not be removed from the registry because both are valid sets, but we decide to ignore one of the two]
We might consider smarter options in many cases (lock a "do not touch" dataset, use Jira for "delete old after new verified", ...), but it is still helpful to remember when and why a lock was set, etc., especially longer-term with staff changes.
Author: mdoering@gbif.org
Created: 2012-07-19 15:46:40.481
Updated: 2012-07-19 15:46:40.481
or implement as jira comments against an issue for each dataset? We do sort of this for checklists already:
http://dev.gbif.org/issues/browse/CLBCONTENT
Author: ahahn@gbif.org
Comment: I am aware of that (we also have it for occurrence data management at http://dev.gbif.org/issues/browse/DM). But unless the relevant messages can be visualised within the indexing operator console directly next to the dataset concerned, they are just too far removed in Jira to allow quick decisions when mass-scheduling a list of indexing operations.
Created: 2012-07-19 16:50:16.316
Updated: 2012-07-19 16:50:16.316
Author: mdoering@gbif.org
Comment: When suggesting jira I expected the comments to be accessible via web services and therefore to be integrated into the console UI - while at the same time also existing in jira
Created: 2012-07-19 16:54:55.251
Updated: 2012-07-19 16:54:55.251
Author: lfrancke@gbif.org
Comment: The thing that put me off of using JIRA for this was that we might have multiple JIRAs open for a single Dataset and would then need to either chose one to display by making it special somehow or display a list of all of them which defeats the purpose of quick visibility. Also that some of them might not really be issues: "testing something, will harvest after lunch" etc.
Created: 2012-07-19 16:59:02.003
Updated: 2012-07-19 16:59:02.003
Author: ahahn@gbif.org
Comment: As long as I and other operators can create, update and read them through the console UI without lengthy navigation, that is fine. The purpose is mainly to make <1sec decisions on whether or not to schedule a dataset for crawling, and to leave brief notes to each other and ourselves. Many of those are not issues that will ever be closed, just messages to keep a history (e.g. why a dataset is excluded from indexing).
Created: 2012-07-19 17:00:26.427
Updated: 2012-07-19 17:00:26.427