Property talk:P5530

Documentation

Altmetric DOI
DOI of a scientific or academic article at altmetric.com, to track citation metrics

Associated item

Altmetric LLP (Q27991349)

Data type

External identifier

Domain

scholarly article (Q13442814), scientific journal (Q5633421) or version, edition or translation (Q3331189)

Allowed values

10.\d{4,9}\/[-._;()\/:A-Za-z0-9]+

Example

Reference ranges for estradiol, progesterone, luteinizing hormone and follicle-stimulating hormone during the menstrual cycle (Q44275619) → 10.15347/WJM/2014.001
Tropical forests and global atmospheric change: a synthesis (Q28764908) → 10.1098/RSTB.2003.1449
Whether weather matters: Evidence of association between in utero meteorological exposures and foetal growth among Indigenous and non-Indigenous mothers in rural Uganda (Q33773228) → 10.1371/JOURNAL.PONE.0179010

Source

https://altmetric.com/

Formatter URL

https://www.altmetric.com/details/doi/$1

Altmetric IDs are not designed to be persistent IDs[edit]

@Diptanshu Das: I was contemplating a massive import of the Altmetric ID, and contacted Altmetric to have their permission ot use their API. I received an answer from them who is, in the context of this property, a game changer IMHO. Extract from the email:

[...] there is a bit of a problem in that the Altmetric IDs are not designed to be persistent IDs. With that in mind, it would be fairly inefficient for you and for our API if you kept those IDs up to date all the time.

I would suggest instead building the URL in the following way:
www.altmetric.com/details/doi/ [doi] - just replace [doi] with the relevant article DOI. It will lead to a details page as long as we have a record for that item. If we do not have a record for the item, it will simply lead to a page stating that we have not received any attention for the item yet. This will be a much easier and more reliable way to link to the Altmetric details page.

Of the 12759 elements with an Altemetric ID, only 52 has no DOI. See this request to retrieve the scientific papers with altmetric but no DOI:

# Scientific paper with altmetric
SELECT ?item ?itemLabel  ?altMetric WHERE {
  # Scientific paper
  ?item wdt:P31 wd:Q13442814.
  ?item wdt:P5530 ?altMetric .
  
  # That doesn't have a a DOI
  FILTER NOT EXISTS { ?item wdt:P356 ?DOI } 

  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}

Try it!

Looking at the results, this 52 articles can probably have their DOI added. I did it for Proteomic identification and characterization of hepatic glyoxalase 1 dysregulation in non-alcoholic fatty liver disease. (Q49742817). Now, both URL https://www.altmetric.com/details/doi/10.1186/s12953-018-0131-y and https://www.altmetric.com/details/33246845 lead to the same article.

Based on the comment by Altmetric, that their ID is not permanent, and since DOI is and can be used to retrieve the right page on Altmetric web site, wouldn't it make sense to move the Altmetric ID to the DOI? We would keep the same Property, but the ID would simply be the DOI. That way, we could then simply create a bot that would check, for any article with a DOI but no Altmetric, if a corresponding page on the Altmetric site exists and, if so, write the Altmetric ID.

Or is there something that would prevent this conversion?

Thanks,

Dirac (talk) 18:49, 1 February 2021 (UTC)[reply]

@Dirac: Thanks for the initiative. I really appreciate your brain storming. The way I see this is that Altmetric had not designed it to be an unique id even though it is and can be. I think that Altmetric people can be convinced to effectively make use of it but somebody needs to take charge. I had done it for the emedicine id (which Wikipedia/Wikidata used but the whole setup was falling apart because emedicine planned to make it redundant but I convinced them to retain it, and they did). I was keen on doing this with this Altmetric id as well but certain adversities I faced from the WikiJournal community prevented me from going ahead. I see significant potential here and it would be great if you can take it ahead. I am not very sure that I should get involved. Your proposal about replacing it with DOI is good but I think more thoughts need to go into it, something that I would restrain myself from doing. Diptanshu 💬 19:23, 3 February 2021 (UTC)[reply]

progressing this property[edit]

@Diptanshu_Das, Dirac, ديفيد عادل وهبة خليل 2, Rachel Helps (BYU), YULdigitalpreservation, ArthurPSmith: The Source MetaData WikiProject does not exist. Please correct the name. The Wikidata for Research WikiProject does not exist. Please correct the name.

Notified participants of WikiProject Medicine

I think Altmetric is very useful and I'd like to take stock and see how we can progress it further

Does anyone know who created the present 12k values? So far I only know of Dirac having done work on it
Dirac, have you tried large-scale access to the Altmetric API, eg for 5-10M DOIs?
- Are Altmetric willing to give us just a dump of DOIs for which they have data, or add a cheaper "existence check" API?
Given the previous section, I agree that Altmetric IDs like 10530629 are not needed (since they are unstable), and DOI should be used instead
- Eg https://www.altmetric.com/details/doi/10.7717/peerj.2331 redirects to https://www.altmetric.com/details/10530629
Maybe we don't need this prop at all and can replace it with a "boolean" claim like has characteristic (P1552) "Altmetric.com page"
- The Altmetric page can be added as a "third party formatter" on DOI (P356)
- Pros: better normalization, eg what happens if a WD item has different DOI and "Altmetric DOI id"?
- Cons: users won't see a clickable link to access the Altmetric page
- We could add the Altmetric URL as qualifier "URL" on the "has quality" claim, but what if Altmetric.com change the format of their URLs?

Cheers! --Vladimir Alexiev (talk) 14:25, 12 December 2021 (UTC)[reply]

@Vladimir Alexiev:, I've contacted Altmetric last February and they replied me some valuable information about their ID:

I spoke with some of my colleagues about this and we are generally very happy for the links to be in WikiData. However there is a bit of a problem in that the Altmetric IDs are not designed to be persistent IDs. With that in mind, it would be fairly inefficient for you and for our API if you kept those IDs up to date all the time. I would suggest instead building the URL in the following way:
www.altmetric.com/details/doi/[doi] - just replace [doi] with the relevant article DOI. It will lead to a details page as long as we have a record for that item. If we do not have a record for the item, it will simply lead to a page stating that we have not received any attention for the item yet. This will be a much easier and more reliable way to link to the Altmetric details page.

I will fix the Altmetric regex to by the same than the DOI, and will update the items with an Altmetric ID to use DOI instead of they other ID.

Answers to your questions below:

Dirac, have you tried large-scale access to the Altmetric API, eg for 5-10M DOIs?
- No. Looking at my notes about Altmetric, it seems that I have everything in hands to proceed though. By reading their API documentation, I see that they have updated their limitation (it was 1 request per second before), and that requesting an API key raises the rate significantly (I have succeeded to see my limit using X-HourlyRateLimit-Limit and X-DailyRateLimit-Limit. Can you?). We could proceed, but the time I have to invest in this is limited. Is it something you have the skills and time to carry on?
- Are Altmetric willing to give us just a dump of DOIs for which they have data, or add a cheaper "existence check" API?
  - We could ask them. If you want to do this, I can forward you the last email I received from Altmetric. Just send me an email through Wikidata and I'll forward it to you.

Looking forward to collaborating with you on this,

Dirac (talk) 16:10, 16 December 2021 (UTC)[reply]

I've updated the formatter URL (P1630) to point to the URL using the DOI (ie. www.altmetric.com/details/doi/[doi]), but it seems it takes between 12 and 48 hours for the ID links to be operational (and that I should have the concensus of the community before proceeding...). I've only updated Causes and consequences of gestational diabetes in South Asians living in Canada: results from a prospective cohort study (Q42367700) to see if the generated URL works. The regexp seems to work (I've also proposed a regexp for DOI, but this is another topic). Once I see that the URL is pointing to the updated AltMetric URL, I'll update the 12 825 other items.

Dirac (talk) 16:55, 16 December 2021 (UTC)[reply]

I've updated the URL format with success. However, I can't find a way in Quick Statement to remove the current value. I am not the only one with this problem. I could add the updated value, but there would be two values: one with correct with the updated URL, and the old one that now leads to a 404 error on the AltMetric web site. See Delirium: a guide for the general physician. (Q48397830) as example. I'll see if I can find a way to remove in batch those values and, if not, I will revert back the URL format to the old one. Dirac (talk) 16:25, 17 December 2021 (UTC)[reply]

Hi! You just need to put quotes around the value, see https://quickstatements.toolforge.org/#/batch/72158 where I was able to remove that value. Also, I'm not sure whether triple quotes around the DOI value will work?

Re consensus on changing the format, I think you got it :-)
My email is my name , at ontotext dot com. I'll pick up the correspondence with Altmetrics Vladimir Alexiev (talk) 15:53, 20 December 2021 (UTC)[reply]

Fill DOI from old Altmetric[edit]

Ok, I see that Dirac has fixed most values to be equal to the DOI. I fixed some more (and the property examples) and now we have almost no discrepancies (I checked these cases, they are valid):

select * {
  ?x wdt:P5530 ?alt; wdt:P356 ?doi
  filter(?alt!=?doi)
}

Try it!

I'll write to Altmetrics to get their DOIs in bulk.

We have 56 cases where we know the old Altmetric id but no the DOI. Any takers to use the Altmetric API to get the DOIs of these items? Then I can push both DOIs and the new Altmetric values.

select * {
  ?x wdt:P5530 ?alt
   filter not exists {?x wdt:P356 ?doi}
}

Try it!

--Vladimir Alexiev (talk) 15:07, 21 December 2021 (UTC)[reply]

Add SPARQL constraint[edit]

Any takers to add a SPARQL constraint "when Altmetric is present, it should be equal to (one of) the DOI"?

I've seen such constraints on some well-described props, I think "birth date" or "death date"?

You can see the comparison query above, or I can adapt it.. But too lazy to lookup how to make the constraint. --Vladimir Alexiev (talk) 15:07, 21 December 2021 (UTC)[reply]

Communication with Altmetric[edit]

Dirac (talk • contribs • logs) gave me the task to communicate with Altmetric. I sent this to info@altmetric.com:

We have adopted your suggestion and fixed the Wikidata prop to "Altmetrics DOI" and fixed all existing values. You can see our progress here: https://www.wikidata.org/wiki/Property_talk:P5530.

Another question: could you please give us just a dump of DOIs for which you have Altmetric data? Wikidata has 27M DOIs as you can see at https://w.wiki/4afw. Hitting your API for each of these DOIs will create a lot of load, and take a lot of time. Alternatively (but more work for you), could you add a cheaper "existence check" API?

--Vladimir Alexiev (talk) 15:21, 21 December 2021 (UTC)[reply]

Altmetrics response: Thank you for contacting us with your query and apologies for not replying sooner, most of the team have been OOO for the last couple of weeks.

We are currently looking into whether we are able to export the data that you have requested, but one of the key decision makers in this, is not in the office this week, so I hope to come back to you next week with whether this is feasible on our end.

--Vladimir Alexiev (talk) 18:40, 21 January 2022 (UTC)[reply]

Property talk:P5530

Contents

Documentation

Altmetric IDs are not designed to be persistent IDs[edit]

progressing this property[edit]

Fill DOI from old Altmetric[edit]

Add SPARQL constraint[edit]

Communication with Altmetric[edit]

Navigation menu

Property talk:P5530

Documentation

Altmetric IDs are not designed to be persistent IDs[edit]

progressing this property[edit]

Fill DOI from old Altmetric[edit]

Add SPARQL constraint[edit]

Communication with Altmetric[edit]

Navigation menu

Search