Discussion
Loading...
Discussion
That would be great! We anyway want to federate link preview metadata (I see there's https://helge.codeberg.page/fep/fep/8967/ though nobody seems to have implemented it yet) so it'd be great if it was done as an extension of that, so that non-scientific platforms can still show a subset of the preview information at least? And yeah looking at existing schemas to reuse sounds great, maybe we can collaborate on a FEP draft that just points to those and shows some examples?
Have you also looked at:
1. https://schema.datacite.org
2. DOI Kernel Schema
3. ORCID seems to use CreativeWork from schema.org (we fetch orcid records in JSON but I'd have to double check what schema that's giving us) https://iphylo.blogspot.com/2020/01/orcid-serves-schemaorg-linked-data-via.html
Currently the UI preview component checks for many different field names for each info, eg: `e(@metadata, "datePublished", nil) || e(@metadata, "publication-date", nil) || e(@metadata, "date", nil) || e(@metadata, "created", "date-time", nil) || e(@metadata, "DC.date", nil) || e(@metadata, "citation_publication_date", nil)` because the data is ingested from multiple sources in different formats, so would be great to instead transform it into a single schema at ingest.
https://github.com/bonfire-networks/bonfire_ui_social/tree/main/lib/components/activity/media/papers
Related issues for reference (feel free to comment there too):
https://github.com/bonfire-networks/bonfire-app/issues/1541
https://github.com/bonfire-networks/bonfire-app/issues/1598
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled