search

bagit-profiles / bagit-profiles-specification

https://bagit-profiles.github.io/bagit-profiles-specification/
Other
35 stars 11 forks source link

Proposing Manifests-Complete #6

Closed stain closed 4 years ago

stain commented 9 years ago

See jkunze/bagitspec#6 which says that manifests are not necessarily individually complete.

I think a profile should be able to restrict this so that a consumer can rely on a fixed list of manifests to be known to be complete lists of the whole payload.

A similar Tag-Manifests-Complete property could be even more useful as the BagIt spec do not require all tagfiles to be listed at all, but would have to specify which tagfiles are excluded (e.g. the tag manifest itself)

mjordan commented 9 years ago

Given the discussion at jkunze/bagitspec#6 this addition makes sense but let's wait until that issue is marked as closed before moving forward with this.

ruebot commented 9 years ago

agreed

ruebot commented 5 years ago

Since there has been a fair bit of discussion on https://github.com/jkunze/bagitspec/issues/6, should we revisit this one again? ...fully acknowledging it's been a really long time since it was originally submitted :weary:

mjordan commented 5 years ago

@stain I'm trying to work backward from this issue... you said at https://github.com/jkunze/bagitspec/issues/6#issuecomment-377246208 that the Bagit spec itself will resolve this but I can't find reference on PR 19 to this being resolved. Are you still of that opinion?

That said, I also have no problem with your initial proposal to add a Tag-Manifests-Complete directive to the Profiles spec since its purpose is to tighten up the Bagit spec.

ruebot commented 4 years ago

I believe this is resolved via https://github.com/jkunze/bagitspec/issues/6#issuecomment-470967885