DataServiceCommunications

From oaibp

Main Page >> Archive

[edit] Data Provider and Service Provider Communications

[edit] DP communicating changes to SPs

• What information does harvester get when there is a DP error?
  • e.g., retryAfter, redirects, 503s
  • https -- allowed or not? (discussion on oai-implementers sep-oct 2004)

• Appropriate ways for DPs to deal with bad harvesters or SPs
  • e.g., frequency of harvests

• Updating of DP - Repoistory life cyle issue see RepositoryLifecycle also

• DP wants to know how SPs are perceiving it
  • SP registry?
  • Selective by DPs and SPs, e.g., DP may only be interested in certain SPs

[edit] SPs communicating with DPs

• SP hopes and expectations
  • strict adherence to OAI protocol http://www.openarchives.org/OAI/openarchivesprotocol.html
  • SPs must be able to communicate needs to DPs
    • What's in it for the DPs?
    • SPs have different needs

• • Add as much information as possible to DP OAI Identify response?

• Negotiating chunk size See also ResumptionTokens

• Communication of SP-preferred metadata practices (Service Provider registry) and see MetadataContent
  • What specific SPs might hope for in their metadata
  • How bad does metadata have to be before specific SPs cannot use it?
  • Preferred encodings
  • Way to dialogue over this
  • Note that search service practice affects discoverability
  • Better information sharing about metadata crosswalks
    • Example implementations of metadata crosswalks for DPs to use
  • What is native metadata format?
    • Avoiding data loss
  • preferred formats, preferred XML schemas?

• Intent of SP
  • Collection development policy
  • Canonical example: "Don't show my metadata at SP if it also has pornography"