home.social

#oaipmh — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #oaipmh, aggregated by home.social.

fetched live
  1. This will be very interesting to a very small group of people: 'For cultural institutions that provide metadata to the data space for cultural heritage, the implementation of IIIF Change Discovery provides an alternative to implementing OAI-PMH.' pro.europeana.eu/post/deliveri

    #MuseTech #IIIF #OAIPMH #metadata #ChangeDiscovery

  2. This will be very interesting to a very small group of people: 'For cultural institutions that provide metadata to the data space for cultural heritage, the implementation of IIIF Change Discovery provides an alternative to implementing OAI-PMH.' pro.europeana.eu/post/deliveri

    #MuseTech #IIIF #OAIPMH #metadata #ChangeDiscovery

  3. This will be very interesting to a very small group of people: 'For cultural institutions that provide metadata to the data space for cultural heritage, the implementation of IIIF Change Discovery provides an alternative to implementing OAI-PMH.' pro.europeana.eu/post/deliveri

    #MuseTech #IIIF #OAIPMH #metadata #ChangeDiscovery

  4. This will be very interesting to a very small group of people: 'For cultural institutions that provide metadata to the data space for cultural heritage, the implementation of IIIF Change Discovery provides an alternative to implementing OAI-PMH.' pro.europeana.eu/post/deliveri

    #MuseTech #IIIF #OAIPMH #metadata #ChangeDiscovery

  5. This will be very interesting to a very small group of people: 'For cultural institutions that provide metadata to the data space for cultural heritage, the implementation of IIIF Change Discovery provides an alternative to implementing OAI-PMH.' pro.europeana.eu/post/deliveri

    #MuseTech #IIIF #OAIPMH #metadata #ChangeDiscovery

  6. The study shows that around half of supposedly "open" repositories are not technically open at all - their OAI-PMH endpoints are broken, outdated, or misconfigured:

    :doi: doi.org/10.1177/01655515251396

    For me, this paper is not a revelation, but a confirmation of a simple point: open science does not start with policies or declarations. It starts with routine infrastructural work - making sure that the basic protocols actually work.

    #OpenScience #FAIRdata #Repositories #OAIPMH

  7. The study shows that around half of supposedly "open" repositories are not technically open at all - their OAI-PMH endpoints are broken, outdated, or misconfigured:

    :doi: doi.org/10.1177/01655515251396

    For me, this paper is not a revelation, but a confirmation of a simple point: open science does not start with policies or declarations. It starts with routine infrastructural work - making sure that the basic protocols actually work.

    #OpenScience #FAIRdata #Repositories #OAIPMH

  8. The study shows that around half of supposedly "open" repositories are not technically open at all - their OAI-PMH endpoints are broken, outdated, or misconfigured:

    :doi: doi.org/10.1177/01655515251396

    For me, this paper is not a revelation, but a confirmation of a simple point: open science does not start with policies or declarations. It starts with routine infrastructural work - making sure that the basic protocols actually work.

    #OpenScience #FAIRdata #Repositories #OAIPMH

  9. The study shows that around half of supposedly "open" repositories are not technically open at all - their OAI-PMH endpoints are broken, outdated, or misconfigured:

    :doi: doi.org/10.1177/01655515251396

    For me, this paper is not a revelation, but a confirmation of a simple point: open science does not start with policies or declarations. It starts with routine infrastructural work - making sure that the basic protocols actually work.

    #OpenScience #FAIRdata #Repositories #OAIPMH

  10. The study shows that around half of supposedly "open" repositories are not technically open at all - their OAI-PMH endpoints are broken, outdated, or misconfigured:

    :doi: doi.org/10.1177/01655515251396

    For me, this paper is not a revelation, but a confirmation of a simple point: open science does not start with policies or declarations. It starts with routine infrastructural work - making sure that the basic protocols actually work.

    #OpenScience #FAIRdata #Repositories #OAIPMH

  11. Für das Deutsche Literaturarchiv in Marbach habe ich vor einiger Zeit einen performanten OAI-PMH-Dienst entwickelt, um die ca. 3,5 Millionen bibliographischen Datensätze standardisiert in verschiedenen Formaten anbieten zu können.

    Die Software ist selbstverständlich quelloffen und jetzt ist endlich auch die Dokumentation fertig.

    #opensource #oaipmh #code4lib

    github.com/opencultureconsulti

  12. Für das Deutsche Literaturarchiv in Marbach habe ich vor einiger Zeit einen performanten OAI-PMH-Dienst entwickelt, um die ca. 3,5 Millionen bibliographischen Datensätze standardisiert in verschiedenen Formaten anbieten zu können.

    Die Software ist selbstverständlich quelloffen und jetzt ist endlich auch die Dokumentation fertig.

    #opensource #oaipmh #code4lib

    github.com/opencultureconsulti

  13. Für das Deutsche Literaturarchiv in Marbach habe ich vor einiger Zeit einen performanten OAI-PMH-Dienst entwickelt, um die ca. 3,5 Millionen bibliographischen Datensätze standardisiert in verschiedenen Formaten anbieten zu können.

    Die Software ist selbstverständlich quelloffen und jetzt ist endlich auch die Dokumentation fertig.

    #opensource #oaipmh #code4lib

    github.com/opencultureconsulti

  14. Für das Deutsche Literaturarchiv in Marbach habe ich vor einiger Zeit einen performanten OAI-PMH-Dienst entwickelt, um die ca. 3,5 Millionen bibliographischen Datensätze standardisiert in verschiedenen Formaten anbieten zu können.

    Die Software ist selbstverständlich quelloffen und jetzt ist endlich auch die Dokumentation fertig.

    #opensource #oaipmh #code4lib

    github.com/opencultureconsulti

  15. Für das Deutsche Literaturarchiv in Marbach habe ich vor einiger Zeit einen performanten OAI-PMH-Dienst entwickelt, um die ca. 3,5 Millionen bibliographischen Datensätze standardisiert in verschiedenen Formaten anbieten zu können.

    Die Software ist selbstverständlich quelloffen und jetzt ist endlich auch die Dokumentation fertig.

    #opensource #oaipmh #code4lib

    github.com/opencultureconsulti

  16. #Handschriftenportal erhält erste Schnittstelle: Der Zugriff auf unseren umfangreichen Datenbestand ist nun per #OAIPMH möglich. Datensets sind als #TEI und #DublinCore verfügbar.

    🔜 Weitere Schnittstellen folgen. Um die Bedarfe der Community besser einschätzen zu können, freuen wir uns über Ihr Feedback: Welche Schnittstellen sind für Ihre Arbeit und Forschung besonders relevant?

    Alle Informationen ➡️ blog.sbb.berlin/hsp-oai-schnit

    @histodons @medievodons

    #digitalhumanities #manuscripts #api

  17. #Handschriftenportal erhält erste Schnittstelle: Der Zugriff auf unseren umfangreichen Datenbestand ist nun per #OAIPMH möglich. Datensets sind als #TEI und #DublinCore verfügbar.

    🔜 Weitere Schnittstellen folgen. Um die Bedarfe der Community besser einschätzen zu können, freuen wir uns über Ihr Feedback: Welche Schnittstellen sind für Ihre Arbeit und Forschung besonders relevant?

    Alle Informationen ➡️ blog.sbb.berlin/hsp-oai-schnit

    @histodons @medievodons

    #digitalhumanities #manuscripts #api

  18. #Handschriftenportal erhält erste Schnittstelle: Der Zugriff auf unseren umfangreichen Datenbestand ist nun per #OAIPMH möglich. Datensets sind als #TEI und #DublinCore verfügbar.

    🔜 Weitere Schnittstellen folgen. Um die Bedarfe der Community besser einschätzen zu können, freuen wir uns über Ihr Feedback: Welche Schnittstellen sind für Ihre Arbeit und Forschung besonders relevant?

    Alle Informationen ➡️ blog.sbb.berlin/hsp-oai-schnit

    @histodons @medievodons

    #digitalhumanities #manuscripts #api

  19. #Handschriftenportal erhält erste Schnittstelle: Der Zugriff auf unseren umfangreichen Datenbestand ist nun per #OAIPMH möglich. Datensets sind als #TEI und #DublinCore verfügbar.

    🔜 Weitere Schnittstellen folgen. Um die Bedarfe der Community besser einschätzen zu können, freuen wir uns über Ihr Feedback: Welche Schnittstellen sind für Ihre Arbeit und Forschung besonders relevant?

    Alle Informationen ➡️ blog.sbb.berlin/hsp-oai-schnit

    @histodons @medievodons

    #digitalhumanities #manuscripts #api

  20. @nilsreiter @DHd

    Das heißt aktuell müsste man Zenodos #oaipmh abgrasen und nach den XML-Einträgen filtern und die scrapen?

  21. @nilsreiter @DHd

    Das heißt aktuell müsste man Zenodos #oaipmh abgrasen und nach den XML-Einträgen filtern und die scrapen?

  22. @nilsreiter @DHd

    Das heißt aktuell müsste man Zenodos #oaipmh abgrasen und nach den XML-Einträgen filtern und die scrapen?

  23. @nilsreiter @DHd

    Das heißt aktuell müsste man Zenodos #oaipmh abgrasen und nach den XML-Einträgen filtern und die scrapen?

  24. Good news from the US Repository Network (#USRN):
    sparcopen.org/wp-content/uploa

    "At the beginning of the project, about half of the #repositories did not have their #OAIPMH interface properly configured and, therefore, could not be indexed by external discovery systems. After just over a year of the pilot, all but one repositories are now OAI-PMH compliant. This has resulted in a 50% increase in indexed content, with 728,770 new records now publicly accessible."

    #GreenOA #ScholComm

  25. Good news from the US Repository Network (#USRN):
    sparcopen.org/wp-content/uploa

    "At the beginning of the project, about half of the #repositories did not have their #OAIPMH interface properly configured and, therefore, could not be indexed by external discovery systems. After just over a year of the pilot, all but one repositories are now OAI-PMH compliant. This has resulted in a 50% increase in indexed content, with 728,770 new records now publicly accessible."

    #GreenOA #ScholComm

  26. Good news from the US Repository Network (#USRN):
    sparcopen.org/wp-content/uploa

    "At the beginning of the project, about half of the #repositories did not have their #OAIPMH interface properly configured and, therefore, could not be indexed by external discovery systems. After just over a year of the pilot, all but one repositories are now OAI-PMH compliant. This has resulted in a 50% increase in indexed content, with 728,770 new records now publicly accessible."

    #GreenOA #ScholComm

  27. Good news from the US Repository Network (#USRN):
    sparcopen.org/wp-content/uploa

    "At the beginning of the project, about half of the #repositories did not have their #OAIPMH interface properly configured and, therefore, could not be indexed by external discovery systems. After just over a year of the pilot, all but one repositories are now OAI-PMH compliant. This has resulted in a 50% increase in indexed content, with 728,770 new records now publicly accessible."

    #GreenOA #ScholComm

  28. Good news from the US Repository Network (#USRN):
    sparcopen.org/wp-content/uploa

    "At the beginning of the project, about half of the #repositories did not have their #OAIPMH interface properly configured and, therefore, could not be indexed by external discovery systems. After just over a year of the pilot, all but one repositories are now OAI-PMH compliant. This has resulted in a 50% increase in indexed content, with 728,770 new records now publicly accessible."

    #GreenOA #ScholComm

  29. There was me still thinking that it'd be good to get around to adding #OAIPMH to a wiki, but now it's probably better spending the effort on #ActivityPub integration. So far, OpenGraph support has been the most useful, and that's super simple in comparison.

  30. There was me still thinking that it'd be good to get around to adding #OAIPMH to a wiki, but now it's probably better spending the effort on #ActivityPub integration. So far, OpenGraph support has been the most useful, and that's super simple in comparison.

  31. There was me still thinking that it'd be good to get around to adding #OAIPMH to a wiki, but now it's probably better spending the effort on #ActivityPub integration. So far, OpenGraph support has been the most useful, and that's super simple in comparison.

  32. There was me still thinking that it'd be good to get around to adding #OAIPMH to a wiki, but now it's probably better spending the effort on #ActivityPub integration. So far, OpenGraph support has been the most useful, and that's super simple in comparison.

  33. @pouyllau on dirait que #Calames va enfin être moissonnée par #Isidore ? c'est une très bonne nouvelle @archivistodon #OAIPMH #archives On attend ça pour la semaine prochaine ?

  34. @pouyllau on dirait que #Calames va enfin être moissonnée par #Isidore ? c'est une très bonne nouvelle @archivistodon #OAIPMH #archives On attend ça pour la semaine prochaine ?

  35. @pouyllau on dirait que #Calames va enfin être moissonnée par #Isidore ? c'est une très bonne nouvelle @archivistodon #OAIPMH #archives On attend ça pour la semaine prochaine ?

  36. @josh Similarly, it's relatively common for #DSpace #OAIPMH endpoints to be styled with #XSLT. For example all the Italian universities have something like this:
    air.unimi.it/oai/request?verb=

    (I see they've recently broken the list of records, it doesn't style the metadata any more. Sad.)

    @eb

  37. @josh Similarly, it's relatively common for #DSpace #OAIPMH endpoints to be styled with #XSLT. For example all the Italian universities have something like this:
    air.unimi.it/oai/request?verb=

    (I see they've recently broken the list of records, it doesn't style the metadata any more. Sad.)

    @eb

  38. @josh Similarly, it's relatively common for #DSpace #OAIPMH endpoints to be styled with #XSLT. For example all the Italian universities have something like this:
    air.unimi.it/oai/request?verb=

    (I see they've recently broken the list of records, it doesn't style the metadata any more. Sad.)

    @eb

  39. @josh Similarly, it's relatively common for #DSpace #OAIPMH endpoints to be styled with #XSLT. For example all the Italian universities have something like this:
    air.unimi.it/oai/request?verb=

    (I see they've recently broken the list of records, it doesn't style the metadata any more. Sad.)

    @eb

  40. @josh Similarly, it's relatively common for #DSpace #OAIPMH endpoints to be styled with #XSLT. For example all the Italian universities have something like this:
    air.unimi.it/oai/request?verb=

    (I see they've recently broken the list of records, it doesn't style the metadata any more. Sad.)

    @eb

  41. @pascaliensis ah, you mean you would use an OAI-PMH endpoint as #reconciliation service directly? What sort of resources would the OAI-PMH endpoint expose? (it does not seem so easy to implement - so far I was just thinking about creating an #OpenRefine project from an #OAIPMH endpoint - and then, if we could reconcile between two OR projects, that could solve your use case I guess)

  42. @pascaliensis ah, you mean you would use an OAI-PMH endpoint as #reconciliation service directly? What sort of resources would the OAI-PMH endpoint expose? (it does not seem so easy to implement - so far I was just thinking about creating an #OpenRefine project from an #OAIPMH endpoint - and then, if we could reconcile between two OR projects, that could solve your use case I guess)

  43. @pascaliensis ah, you mean you would use an OAI-PMH endpoint as #reconciliation service directly? What sort of resources would the OAI-PMH endpoint expose? (it does not seem so easy to implement - so far I was just thinking about creating an #OpenRefine project from an #OAIPMH endpoint - and then, if we could reconcile between two OR projects, that could solve your use case I guess)

  44. @pascaliensis ah, you mean you would use an OAI-PMH endpoint as #reconciliation service directly? What sort of resources would the OAI-PMH endpoint expose? (it does not seem so easy to implement - so far I was just thinking about creating an #OpenRefine project from an #OAIPMH endpoint - and then, if we could reconcile between two OR projects, that could solve your use case I guess)

  45. @pascaliensis ah, you mean you would use an OAI-PMH endpoint as #reconciliation service directly? What sort of resources would the OAI-PMH endpoint expose? (it does not seem so easy to implement - so far I was just thinking about creating an #OpenRefine project from an #OAIPMH endpoint - and then, if we could reconcile between two OR projects, that could solve your use case I guess)

  46. If #OpenRefine could import data from an #OAIPMH endpoint, would anyone want to use that? To do what?

  47. If #OpenRefine could import data from an #OAIPMH endpoint, would anyone want to use that? To do what?

  48. If #OpenRefine could import data from an #OAIPMH endpoint, would anyone want to use that? To do what?

  49. If #OpenRefine could import data from an #OAIPMH endpoint, would anyone want to use that? To do what?

  50. If #OpenRefine could import data from an #OAIPMH endpoint, would anyone want to use that? To do what?

  51. Just learned about Data Portal software #piveau piveau.de used at data.europa.eu and open.nrw among others. The RDF-based discovery interface can be used to harvest (e.g. via #OAIPMH) and present datasets published elsehere (e.g. via #CKAN).

  52. Just learned about Data Portal software #piveau piveau.de used at data.europa.eu and open.nrw among others. The RDF-based discovery interface can be used to harvest (e.g. via #OAIPMH) and present datasets published elsehere (e.g. via #CKAN).

  53. Just learned about Data Portal software #piveau piveau.de used at data.europa.eu and open.nrw among others. The RDF-based discovery interface can be used to harvest (e.g. via #OAIPMH) and present datasets published elsehere (e.g. via #CKAN).