We have three platforms where we discuss or document our annotation work

We have three platforms where we discuss or document our annotation work:

Slack for discussing vocabulary and reporting issues with the annotation tools
Confluence for documenting guidance and reporting vocabulary issues
JIRA where vocabulary issue tickets are logged and software development work is tracked

Who has access?

Cochrane Information Specialists
Anyone who is working on Linked Data projects

Slack

What do we use Slack for?

to communicate directly with each other or in groups, either written or by calling
to post queries and suggestions in the #annotation channel
to share files and posts
we post udpates on annotation guidance or tool development, and troubleshooting

What can I post to the annotation channel?

comments & suggestions
general questions about annotation issues
request for help with annotations (or if you want someone to check your annotation)
reporting issues with the tools

How do I post to the #annotation channel

just type and hit your enter key
to alert a particular member of the team insert @ before their name
remember that posts in this channel can be viewed by all members

How do I send a direct (private) message

If you wish to send a private message to one or more people use the direct message option:

Click on + beside Direct Message at the bottom of the lefthand column
Begin to type name of contact in the search box and the name will arrive at the top of the list beneath the search box
Enter multiple names if you wish to create a group
When ready click on GO

Confluence

What do we use Confluence for?

storing our guidanace documents
creating spaces and pages for keeping notes
requesting terms

CRG Space

Each CRG has their own Space in Confluence where they can store any documentation related to their annotation work - how you want to use this space is entirely up to you!
On the main page of this Space a form has been provide for reporting vocabulary issues
To find your Space click on found on the blue menu bar at the top of the page, and then on Space directory to search
Information on how to add new pages or edit existing ones in your Space can be found HERE.

Do NOT remove coding from HTML box when editing Space home page

CRGs can add and remove any information as they wish however it is important not to remove the coding in the HTML box as this will disable the reporting form for vocabulary requests.

Annotation Guidance

Annotation Knowledge Base is where we store our guidance

Block email notifications

When changes are being made to various pages you may receive a number of unwanted email alerts. If you wish to block them please see Blocking notifications from Confluence.

JIRA

JIRA is used for project and issue tracking for both vocabulary and tool issues, and tool development.

LDD and

LDO

We have two boards LDD and LDO where we can monitor and track progress of all logged issues.

Boards	Full title	Description
LDD	Linked Data Development	This board logs tooling related issues such as, ongoing and new development work, bugs, global changes needed for annotation interface etc.
LDO	Linked Data Ontology	This board logs vocabulary related issues such as, terms to be added or merged, etc.

Terms requested using the Report a Vocabulary Issue form

Each request generates a JIRA ticket which in turn creates further discussion about individual terms on JIRA. If you are asked for feedback about a vocab request, you will receive an email notification from JIRA. To respond to these messages, click on the JIRA link for the vocab request within the email (rather than responding to the email). You will be prompted to enter your JIRA ID and password. You can then leave comments on the JIRA page for that request.

Open Vocabulary Issues page shows progress of JIRA tickets.

Status	Description
Done	the vocab issue is fixed & ready to use in Live
Ready for Editor	should be fixed very soon
Ready for Development	not something we can fix with the editor, but ready for us to pass on to DataLanguage
Solution Identified	we could fix it with the editor, but we're waiting for some development from DataLanguage, e.g. there are several vocab requests that will be fixed with LDO 278
Consultation	we have asked one or more Information Specialists for their expertise

Responding to comments on my JIRA ticket term request

Sometimes more information is required from the requester and this is inserted as a comment on the the JIRA ticket that was generated for the specific request. This in turn will generate an email alert to be sent to the requester. To respond we ask that you click on the link to the ticket within the email rather than responding to the email.

	Action	Image
1	Click on the JIRA ticket link (title of request) within the email that you receive to your email inbox
2	If not already logged in you will be prompted to enter your JIRA/Confluence user ID and password
3	Once logged in click on Comment to leave any further information that was requested by Deirdre or Lorne. Remember to alert them, insert @ before their names. When finished click on Add.