Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create glossary Working Group #46

Closed
3 tasks done
rmbaxter67 opened this issue Dec 6, 2023 · 23 comments
Closed
3 tasks done

Create glossary Working Group #46

rmbaxter67 opened this issue Dec 6, 2023 · 23 comments
Assignees
@rmbaxter67
Labels
resources Resources for the community. Use this repo to collate ideas/discussions, move to website when ready

Comments

@rmbaxter67
Copy link

rmbaxter67 commented Dec 6, 2023 •
edited
Loading

Detail

The cross-project TRE-and-related-concepts glossary developed during the DARE UK driver projects is currently on Google Docs. It's a great starting point for a generally useful UK-wide one. It could be hosted at GH/DAREUK, or it could be hosted here. I'd like to see it here. Appropriate?

Actions

Who can help

@rmbaxter67
@manics
Copy link
Member

manics commented Dec 6, 2023

I support creating a new repo in this org (probably another readthedocs site since it's the easiest?) to host the glossary. I think the first question is to agree who has the authority to resolve all the suggestions on the google doc, as this is the work of several projects. Once we agree that I'm happy to help setup the site and convert the gdoc.

@rmbaxter67
Copy link
Author

Quick answer is probably nobody. We could make a proposal to the mailing list, saying: here's a useful vocab; we'd like to host it on UK-TRE; we propose to take the latest snapshot, accept all changes, convert all major comments into issues and put it here. I'm happy to do this, as sponsor of the original projects (which might give my enough authority to make the proposal at least!).

I'd suggest we not import any project or product-specific info but just keep to general terms.

@manics
Copy link
Member

manics commented Dec 6, 2023

Sounds good to me!

@rmbaxter67
Copy link
Author

Suggestion from the list from Milan M: could we also integrate the vocabulary that was created to describe various activities and entities involved in the data linkage process that we have mapped out when we were looking at the Grampian Safe Haven ? They could potentially be seen as more detailed elements of the workflow (which is already mentioned in the glossary). It would be good to get insights from others to see how well this vocabulary maps onto the activities in other TREs https://tre-provenance.github.io/SHP-ontology/releases/v0.2/index-en.html

@harisood
Copy link
Member

harisood commented Dec 7, 2023

This feels like it fits with @crickpetebarnsley & @hardakerm's suggestion for a TRE/SDE terminology working group - not sure if you guys have thoughts!

Do we need a new repo? Slightly concerned about repo overload... could it not be simpler for now to keep it as a Google Doc, for which only the people running the working group have edit access? And everyone else suggest access only. Could still name and tag versions from this and keeps it non-technical for now, we can also point to it from the UK TRE site

@jim-smith
Copy link

Happy to volunteer some time from SDC-Reboot Community of interest to add in relevant terms from the glossary we created for the GRAIMatter project describing AI models, risk types, and legal issues surrounding them

@manics
Copy link
Member

manics commented Dec 11, 2023

Do we need a new repo? Slightly concerned about repo overload... could it not be simpler for now to keep it as a Google Doc

I think it depends on how we want people to use the Glossary. If it's still in development then leaving it as a Google doc is fine, and we don't need to bother with versions. If we want people to use it as a reference, e.g. in their website or formal documents, then I think it needs to be a proper webpage. Using FAIR as a guide:

  • Findable: we can link to google doc but it's not easily searchable outside of GDocs
  • Interoperable: it's not, you need to load a large Javascript application to view it, and you can't easily link to terms
  • Accessible: it's not, you need to load a large Javascript application to view it
  • Reusable: you can copy and paste it though you'll have to reformat it if it's outside Gdocs

I'm happy to keep using GDocs if you want to treat it as under development and not as a reference.

@manics
Copy link
Member

manics commented Dec 11, 2023 •
edited
Loading

Also I discovered Datamind has a nice online glossary
https://datamind.org.uk/glossary/

Are there any other TRE glossaries? How do we manage all of them?

@rmbaxter67
Copy link
Author

rmbaxter67 commented Dec 12, 2023 •
edited
Loading

Our problem here may not be a lack of glossaries but a bounty of glossaries we don't know about! Maybe start a simple resource webpage that collects pointers to ones we learn about. Then we can take a view about what (if anything) is missing and whether to compile Yet Another Glossary or a Glossary of Glossaries. (apols to @harisood !)

@harisood harisood moved this from Ideas to In Progress in TRE Community - project board Dec 12, 2023
@harisood
Copy link
Member

YAG or a GoG

What do these acronyms mean 😅

I agree that it would be good to combine the glossaries we have, and determine where what exists is good enough, where there are conflicts, and whether we need our own one

@Davsarper Davsarper added the resources Resources for the community. Use this repo to collate ideas/discussions, move to website when ready label Jan 9, 2024
@rmbaxter67
Copy link
Author

rmbaxter67 commented Jan 9, 2024 •
edited
Loading

A thought on reconciling (a number of *) existing glossaries: dictionary entries often have multiple definitions, because, well, language. Why not copy that in a common glossary, and: where definitions differ only slightly, merge them; where definitions differ for good reasons of context, etc, list them as separate definitions, tagged with an abbreviation for the source -- eg, DM (DataMind), SP (SHP Ontology), etc.

* I wouldn't suggest we look beyond a half-dozen or so, most of which have been mentioned above.

@harisood
Copy link
Member

@rmbaxter67 to have a conversation with @hardakerm about whether this fits into her and Pete's WG

@hardakerm
Copy link

had conversation with @rmbaxter67 and think it's not likely that this will coincide with the SDE/TRE definitions WG scope, but we will keep lines of communication open

@rmbaxter67
Copy link
Author

rmbaxter67 commented Feb 9, 2024 •
edited
Loading

Over on Google Docs is my first pass spreadsheet. I've merged the DARE UK Drivers glossary with the DataMind glossary -- with astonishingly little overlap.

I've added a "context" column to the DARE glossary to match the "category" column in DataMind.

I also highlighted some project-specific terms (on each side) that I think should go.

I've a blank sheet waiting to ingest the SHP Ontology glossary but haven't figured out a neat way to scrape that yet.

@KirstieJane
Copy link

This is really important work @rmbaxter67 ! Strong support for a glossary working group - and also some "term of the week" or "metadata conflict of the month" community engagement vectors!

@Davsarper
Copy link
Contributor

It was discussed and agreed to turn this into a WG (to be further defined)

@harisood harisood changed the title Host common glossary here? Create glossary Working Group Feb 20, 2024
@harisood
Copy link
Member

@rmbaxter67 I've changed the title, added an action to formulate a WG, and will move this back to backlog!

@harisood harisood moved this from In Progress to Backlog in TRE Community - project board Feb 20, 2024
@harisood harisood moved this from Backlog to In Progress in TRE Community - project board Apr 16, 2024
@rmbaxter67
Copy link
Author

Creation started with request for Jiscmail list, uk-tre-glossary@...
Will populate with named folk from March UK TRE session (me, Balint, Kate O'Sullivan and Will Crocombe) and advertise on uk-tre-community.

@rmbaxter67
Copy link
Author

Working group charter now in development; aim to knock on the head on 29 April. Co-chairs engaged. Mailing list set up. Action here is complete.

@Davsarper
Copy link
Contributor

Hi @rmbaxter67 can you share a view only link that we can circulate with everyone?

@rmbaxter67
Copy link
Author

rmbaxter67 commented Apr 26, 2024 via email

@Davsarper
Copy link
Contributor

Davsarper commented Apr 26, 2024 via email

@manics
Copy link
Member

manics commented May 14, 2024

Created! Charter in progress, will be a separate issue

@manics manics closed this as completed May 14, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in TRE Community - project board May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rmbaxter67 rmbaxter67

Labels
resources Resources for the community. Use this repo to collate ideas/discussions, move to website when ready
Projects
TRE Community - project board
Status: Done
Milestone
No milestone
Development

No branches or pull requests
7 participants
@manics @KirstieJane @jim-smith @harisood @Davsarper @rmbaxter67 @hardakerm