-
Notifications
You must be signed in to change notification settings - Fork 6
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.
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
Updating oboInOwl:created_by to dcterms:contributor for old terms created by ORCID-less contributors #1459
Comments
Does prefixing with "FBC:" stop the check failing? |
Great you are looking into this! I would suggest the following:
If 2 is too much work, I would suggest you use dcelements:contributor for all case where the range is a string, and append a prefix "Flybase:mmc24". Definitely avoid your solutions 3 and 4. |
actually there are not that many creators in FBbt: (from |
temj2 is my direct predecessor, Tamsin Jones - http://orcid.org/0000-0002-0027-0858 |
@Clare72 : No, Thanks for the ORCID above. @matentzn : Will create Wikidata entries if needed (if we can’t identify remaining contributors). |
According to the SourceForge pages of the OBO Foundry (didn’t know someone was still using SourceForge…):
That leaves And I agree about deleting |
For the camcur, I would like to add that we do give credit to groups in a few ontologies, and it is not redundant to do so. You could use wikidata:Q3074571 (https://www.wikidata.org/entity/Q3074571 ) |
On 21 Jul 2022, at 13:27, Nico Matentzoglu ***@***.***> wrote:
For the camcur, I would like to add that we do give credit to groups in a few ontologies, and it is not redundant to do so. You could use wikidata:Q3074571 (https://www.wikidata.org/entity/Q3074571 <https://www.wikidata.org/entity/Q3074571> )
Gillian Millburn was a very major camcur contributor, (for all ontologies but especially FBcv phenotypes) so you might want to ask her if she wants direct credit each time Camcur is used - in addition to the Wikidata FlyBase reference.
… —
Reply to this email directly, view it on GitHub <#1459 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA3RR7EPAZLP6YPSIOVBDLVVE64JANCNFSM54EMB65A>.
You are receiving this because you were mentioned.
|
Remaining contributors referenced from within FBbt by their name rather than an identifier:
|
orcids look good (yes you have the right Kei Ito) |
maybe we could use these for the others: |
As part of the OBO-wide move from
http://www.geneontology.org/formats/oboInOwl#created_by
tohttp://purl.org/dc/terms/contributor
, we want to massively replace all the existingoboInOwl:created_by
annotations in FBbt (and also in other FlyBase ontologies).However, many of the existing
oboInOwl:created_by
annotations in FBbt have a value that is not an ORCID URI, and actually not even an URI at all. Instead, they have values that typically correspond to the initials of the FlyBase ontologist who created them, such asdjs93
,mmc46
,sr544
, etc. Overall, generalised use of ORCIDs only started a few years ago, so almost all “old” terms have a non-ORCID, non-URI creator.But the ODK is now enforcing that all
dcterms:contributor
annotations should have an URI-like value (as part of theiri-range-violation.sparql
standard check), so blindly replacingoboInOwl:created_by
bydcterms:contributor
results in a build failure because annotations likedcterms:contributor mmc46
violate that constraint.@matentzn You’re the one who is keen to see
oboInOwl:created_by
(along withoboInOwl:creation_date
) replaced with equivalent DC terms, so your input here would be welcome: How should old, ORCID-less contributors be dealt with?oboInOwl:created_by
annotations; replaceoboInOwl:created_by
bydcterms:contributor
only when the contributor is represented by an IRI (typically an ORCID URI).Probably not very satisfying if the goal is to get rid of
oboInOwl:created_by
, as that would leave quite a large number of such annotations.I don’t think this is realistically feasible for old contributors that may not even work for FlyBase anymore.
iri-range-violation.sparql
constraint to excludedcterms:contributor
from the list of annotations that must have a IRI value.If we go that route it should be done at the ODK level.
iri-range-violation.sparql
check in FBbt.Doesn’t require any change at the ODK level, but then we lose the benefit of that check entirely, I am not really keen to do that.
For example, transform
mmc46
into something likehttp://flybase.org/contributors/mmc46
. This can be done even if said contributor is no longer there (contrary to creating an ORCID). The constructed pseudo-URI would not resolve to anything meaningful, though, contrary to an ORCID. (Unless we ask our web developers to make those URIs point to something on our website, but that seems way overkill to me.)The text was updated successfully, but these errors were encountered: