OBOFoundry
Review less frequently used elements in the metadata
Btw, here's the table with fields that are used a maximum of 15 times:
| key | ontologies |
|---|---|
| label | ms, xlmod, epio, one, ons, cl, uberon, nomen, go, mondo |
| integration_server | ms, obi, xlmod, cl, go |
| releases | labo, miapa, uberon |
| documentation | ero, pr, ro |
| canonical | cl, uberon, nomen, ro, mondo |
| doid, chebi, ddpheno, hp, go, uberon, disdriv, ddanat, po | |
| depicted_by | stato, obi, chebi, mondo, so, iao, uberon, fypo, eupath, ogms, go, pr, bfo |
| in_foundry | uo, bcgo, flu, fix, bco, obcs, zfs, epo, lipro, stato, omit |
| review | doid, pato, obi, chebi, xao, bfo, zfa, go, pr, po |
| in_foundry_order | doid, pato, obi, chebi, xao, bfo, zfa, go, pr, po |
| funded_by | nomen, uberon, eco |
| wasDerivedFrom | ncbitaxon |
| slack | uberon |
| wikidata_template | uberon |
EDIT by @matentzn : make links work to show configs
Originally posted by @cthoyt in https://github.com/OBOFoundry/OBOFoundry.github.io/pull/1800#issuecomment-1038993141
I realise this is (1) not a priority (as is obvious by the fact that nobody has reacted to that issue in 2 years) and (2) potentially a sensitive topic, but:
Could we least drop the twitter element?
It may have been fine at a time that Twitter was (considered as) the social network and there was not really any other player around, but that is no longer the case (I would argue that this has in fact never been the case). Between the Fediverse, BlueSky, Threads, ~~Truth Social~~, and possibly others that I am not even aware of, there is a diversity of social networks and I see no reason for hardcoding support for Twitter specifically.
In fact, having support for mentioning a Twitter handle specifically, and not any other kind of networks, could now be interpreted as an endorsement of Twitter.
I’d vote for dropping the twitter element and either (a) do nothing else, that is, no longer allow to mention any social network account at all, or (b) replace it by a generic social_networks element accepting arbitrary profile URLs, as in:
social_networks:
fediverse: <URL to Fediverse profile, if any>
twitter: <URL to Twitter/X profile, if any>
bluesky: <URL to Bluesky profile, if any>
...
agreed!
On Sun, Dec 22, 2024 at 4:48 AM Damien Goutte-Gattat < @.***> wrote:
I realise this is (1) not a priority (as is obvious by the fact that nobody has reacted to that issue in 2 years) and (2) potentially a sensitive topic, but:
Could we least drop the twitter element?
It may have been fine at a time that Twitter was (considered as) the social network and there was not really any other player around, but that is no longer the case (I would argue that this has in fact never been the case). Between the Fediverse, BlueSky, Threads, Truth Social, and possibly others that I am not even aware of, there is a diversity of social networks and I see no reason for hardcoding support for Twitter specifically.
In fact, having support for mentioning a Twitter handle specifically, and not any other kind of networks, could now be interpreted as an endorsement of Twitter.
I’d vote for dropping the twitter element and either (a) do nothing else, that is, no longer allow to mention any social network account at all, or (b) replace it by a generic social_networks element accepting arbitrary profile URLs, as in:
social_networks: fediverse: <URL to Fediverse profile, if any> twitter: <URL to Twitter/X profile, if any> bluesky: <URL to Bluesky profile, if any> ...
— Reply to this email directly, view it on GitHub https://github.com/OBOFoundry/OBOFoundry.github.io/issues/1801#issuecomment-2558412665, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJR55QCAJHGNHIQUD7Z2MD2G2KGVAVCNFSM6AAAAABUBQ3NHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGQYTENRWGU . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I agree as well.
On 12/22/2024 10:44 AM, Bill Hogan wrote:
agreed!
On Sun, Dec 22, 2024 at 4:48 AM Damien Goutte-Gattat < @.***> wrote:
I realise this is (1) not a priority (as is obvious by the fact that nobody has reacted to that issue in 2 years) and (2) potentially a sensitive topic, but:
Could we least drop the twitter element?
It may have been fine at a time that Twitter was (considered as) the social network and there was not really any other player around, but that is no longer the case (I would argue that this has in fact never been the case). Between the Fediverse, BlueSky, Threads, Truth Social, and possibly others that I am not even aware of, there is a diversity of social networks and I see no reason for hardcoding support for Twitter specifically.
In fact, having support for mentioning a Twitter handle specifically, and not any other kind of networks, could now be interpreted as an endorsement of Twitter.
I’d vote for dropping the twitter element and either (a) do nothing else, that is, no longer allow to mention any social network account at all, or (b) replace it by a generic social_networks element accepting arbitrary profile URLs, as in:
social_networks: fediverse: <URL to Fediverse profile, if any> twitter: <URL to Twitter/X profile, if any> bluesky: <URL to Bluesky profile, if any> ...
— Reply to this email directly, view it on GitHub
https://github.com/OBOFoundry/OBOFoundry.github.io/issues/1801#issuecomment-2558412665,
or unsubscribe
. You are receiving this because you are subscribed to this thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/OBOFoundry/OBOFoundry.github.io/issues/1801#issuecomment-2558497527, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJB7CRVNX2PPUKS4VN5X3T2G3M5NAVCNFSM6AAAAABUBQ3NHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGQ4TONJSG4. You are receiving this because you are subscribed to this thread.Message ID: @.***>
Yes, great idea, @gouttegd. I hope adding a flexible multi-element field like that isn't too much of a pain.
FWIW, bluesky seems to be rapidly rising to replace xwitter in the scienceverse.
Agree. I suggest a variant of B. Have explicit opt in per group to retain an entry for twitter, mentioning that OBO itself no longer uses it and focuses presence on LinkedIn or fedi or Bsky (or hopefully we will). I suspect many or all will drop it.
On Sun, Dec 22, 2024 at 2:48 AM Damien Goutte-Gattat < @.***> wrote:
I realise this is (1) not a priority (as is obvious by the fact that nobody has reacted to that issue in 2 years) and (2) potentially a sensitive topic, but:
Could we least drop the twitter element?
It may have been fine at a time that Twitter was (considered as) the social network and there was not really any other player around, but that is no longer the case (I would argue that this has in fact never been the case). Between the Fediverse, BlueSky, Threads, Truth Social, and possibly others that I am not even aware of, there is a diversity of social networks and I see no reason for hardcoding support for Twitter specifically.
In fact, having support for mentioning a Twitter handle specifically, and not any other kind of networks, could now be interpreted as an endorsement of Twitter.
I’d vote for dropping the twitter element and either (a) do nothing else, that is, no longer allow to mention any social network account at all, or (b) replace it by a generic social_networks element accepting arbitrary profile URLs, as in:
social_networks: fediverse: <URL to Fediverse profile, if any> twitter: <URL to Twitter/X profile, if any> bluesky: <URL to Bluesky profile, if any> ...
— Reply to this email directly, view it on GitHub https://github.com/OBOFoundry/OBOFoundry.github.io/issues/1801#issuecomment-2558412665, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAMMOMJMLXDTOWNJ25H72L2G2KGRAVCNFSM6AAAAABUBQ3NHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGQYTENRWGU . You are receiving this because you are subscribed to this thread.Message ID: @.***>
