Requirements --> GitHub issues

OK folk, I broke down and did one manually to illustrate what I was hoping could be done automatically. corresponds to

I copied the link to the UCR document into the issue.
I gave it the following labels

(i)                  [requirement]

(ii)                [dcat] according to the deliverable-related tag inherited from Use Case that generated the requirement

Putting it in a standard issue-tracker allows us to follow the progress of satisfying this requirement, or re-classifying it by changing the labels (tags) if necessary.
I just used the text from the UCR document directly, which includes the sub-heading number (6.1.1 in this case) which may be non-persistent if the UCR document is revised. On the other hand, the code [RDID] is also visible, which I think was intended to be a persistent identifier.

This issue is now found by a standard query for

-          Issues tagged [dcat]


-          Issues tagged [dcat] and [requirement]


I also see that Jaro has done a lot of clever Javascripting to get similar selection functions into the UCR document itself but I suggest that if we can use a generic tool (GitHub) which also does the dynamic record-keeping, then maybe we can reduce the need for bespoke scripting moving forward.


Simon J D Cox
Research Scientist
Environmental Informatics
CSIRO Land and Water<>

E<> T +61 3 9545 2365 M +61 403 302 672
   Mail: Private Bag 10, Clayton South, Vic 3169
   Visit: Central Reception, Research Way, Clayton, Vic 3168
   Deliver: Gate 3, Normanby Road, Clayton, Vic 3168<><><><><>

The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.

Please consider the environment before printing this email.

Received on Wednesday, 17 January 2018 05:17:20 UTC