Child pages
  • Audit

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Although the Fixity service will be integrated with Merritt, it is designed as an independent micro-service. As such, it can verify objects inside of Merritt or any arbitrary web-accessible resources. Would you expect to use this feature of the service to verify content existing outside of Merritt?
  • Any fixity violations detected by the service are reported only to the service provider, that is, to UC3 staff, not to the owners or curators of the content. The idea behind this is that the most likely cause of fixity violations is some sort of hardware failure, which can be best responded to by UC3 staff. Do you envision use cases in which you would want to receive to notifications of violations directly? Are there other kinds of reporting of fixity results would you expect?