You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
9/23/2024 - Emailed Patrick Hargitt to check back on status of ROR adoption / Crossref issues. Note that Atypon Literatum is now Atypon Experience Platform.
5/31/2024 - Spoke with Patrick Hargitt of Atypon at SSP 2024. They can't use ROR until they've updated their Crossref schema. They've run into technical problems with that and are working on them with Crossref. ***
2/21/24 Reached out to Rae de Guzman on LinkedIn -- no reply
4/20/23 Meeting with Fatima Abu Lawi
Fatima is a Product Manager who works on Atypon Literatum, which deposits metadata to Crossref, Pubmed, ISI, and Google feeds. They have 63 clients who send them XML which they then use to register DOIs with Crossref and similar third parties such as Pubmed, ISI, and Google Feeds. They don't add the ROR IDs for the publishers. Publishers upload content files to Literatum and then can edit the XML in the admin interface.
They are currently working to upgrade to using the 5.3.1 schema for Crossref, which should be complete between May and July 2023. They will do a demonstration to account managers, then will give publishers two weeks notice about the change, then will announce in a blog post.
Fatima agreed to provide an example from their testing (since it's not live yet) of the XML they will send to Crossref with a ROR ID. She will also send the blog post when it's done, though Amanda is subscribed to the Atypon newsletter. Fatima will also have a product manager from ResearchExchange reach out. Amanda will provide some slides about the business value of ROR, how it can (e.g.) raise the profile of content in search results. Amanda will also provide information about mapping ROR IDs to other IDs and matching text strings to ROR IDs.
4/12/23 Messaged Jeffrey Plautz on LinkedIn
Jeffrey referred me to Fatima Abu Lawi
Communicating with Dawn Ingram of Atypon via Crossref support about messy Ringgold data in Wiley publications
The text was updated successfully, but these errors were encountered:
9/23/2024 - Emailed Patrick Hargitt to check back on status of ROR adoption / Crossref issues. Note that Atypon Literatum is now Atypon Experience Platform.
5/31/2024 - Spoke with Patrick Hargitt of Atypon at SSP 2024. They can't use ROR until they've updated their Crossref schema. They've run into technical problems with that and are working on them with Crossref. ***
2/21/24 Reached out to Rae de Guzman on LinkedIn -- no reply
4/20/23 Meeting with Fatima Abu Lawi
Fatima is a Product Manager who works on Atypon Literatum, which deposits metadata to Crossref, Pubmed, ISI, and Google feeds. They have 63 clients who send them XML which they then use to register DOIs with Crossref and similar third parties such as Pubmed, ISI, and Google Feeds. They don't add the ROR IDs for the publishers. Publishers upload content files to Literatum and then can edit the XML in the admin interface.
They are currently working to upgrade to using the 5.3.1 schema for Crossref, which should be complete between May and July 2023. They will do a demonstration to account managers, then will give publishers two weeks notice about the change, then will announce in a blog post.
Fatima agreed to provide an example from their testing (since it's not live yet) of the XML they will send to Crossref with a ROR ID. She will also send the blog post when it's done, though Amanda is subscribed to the Atypon newsletter. Fatima will also have a product manager from ResearchExchange reach out. Amanda will provide some slides about the business value of ROR, how it can (e.g.) raise the profile of content in search results. Amanda will also provide information about mapping ROR IDs to other IDs and matching text strings to ROR IDs.
4/12/23 Messaged Jeffrey Plautz on LinkedIn
Jeffrey referred me to Fatima Abu Lawi
Communicating with Dawn Ingram of Atypon via Crossref support about messy Ringgold data in Wiley publications
The text was updated successfully, but these errors were encountered: