Arvados

Ready for first look in f7f5dfb456c1ddb6db63cf6e6a79e5d468d20a20 on 16421-document-collection-deletion-lifecycle

Pushed missing files in 8a00acc17403e7836b88b1e9e66b4ff47d5505f2

Ward Vandewege wrote:

Ready for first look in f7f5dfb456c1ddb6db63cf6e6a79e5d468d20a20 on 16421-document-collection-deletion-lifecycle

Recovering data¶

I usually try to have a brief introduction at the top, like, "Arvados has several features to prevent accidental loss/deletion of data, but accidents happen..."

Mention data recovery can be used for both deleting collections and overwritten collection contents.

Link to "Data lifecycle" architecture page.

Tell user to look in the trash first.

Tell user collection contents may be available somewhere else and try searching by PDH.

Mention/link to collection versioning as a way to prevent accidental overwriting of collection contents.

When mentioning configuration items, include the section, eg AuditLogs.UnloggedAttributes, AuditLogs.MaxAge, Collections.BlobMissingReport

"Obviously this could be improved ..." if it is obvious you don't need to say it, but then raises the question of why the example doesn't do it.

Architecture¶

I would tweak the section labels to avoid parenthesis, something like "Storage in Keep" and "Computation with Crunch"

"Keep - Content-Addressable Storage" the leading "Keep" in the title is redundant.

I would reorder the pages:

1. Content-Addressable Storage
2. Keep clients
3. Manifest format
4. Data lifecycle

User guide¶

On "Keep collection lifecycle" there's a section "Collection lifecycle attributes" which is mostly a duplicate of the "Data lifecycle" page, it should just link to that page instead.

Peter Amstutz wrote:

Ward Vandewege wrote:

Ready for first look in f7f5dfb456c1ddb6db63cf6e6a79e5d468d20a20 on 16421-document-collection-deletion-lifecycle

Recovering data¶

I usually try to have a brief introduction at the top, like, "Arvados has several features to prevent accidental loss/deletion of data, but accidents happen..."

Mention data recovery can be used for both deleting collections and overwritten collection contents.

Link to "Data lifecycle" architecture page.

Tell user to look in the trash first.

Tell user collection contents may be available somewhere else and try searching by PDH.

Mention/link to collection versioning as a way to prevent accidental overwriting of collection contents.

OK, I've made a bunch of changes along those lines. I've also reduced duplication in the user guide, by making the "Keep lifecycle" page there just about "Trashing and untrashing data", linking to the main "Collection lifecycle" page in the Architecture section.

When mentioning configuration items, include the section, eg AuditLogs.UnloggedAttributes, AuditLogs.MaxAge, Collections.BlobMissingReport

Fixed.

"Obviously this could be improved ..." if it is obvious you don't need to say it, but then raises the question of why the example doesn't do it.

I dropped that line. That code is mostly redundant, the new recover-collections tool is the better way to get out of that situation. But it's helpful to show the 'manual way' so that the admin can see that there is a manual way that is not complicated. Increases confidence.

Architecture¶

I would tweak the section labels to avoid parenthesis, something like "Storage in Keep" and "Computation with Crunch"

OK done.

"Keep - Content-Addressable Storage" the leading "Keep" in the title is redundant.

The title in the menu is also the title of the page. So I want to keep the word 'Keep' in there. I've renamed it to 'Introduction to Keep'.

I would reorder the pages:

1. Content-Addressable Storage
2. Keep clients
3. Manifest format
4. Data lifecycle

Done, though I swapped the lifecycle and manifest format pages, the latter being lower level.

User guide¶

On "Keep collection lifecycle" there's a section "Collection lifecycle attributes" which is mostly a duplicate of the "Data lifecycle" page, it should just link to that page instead.

Ah, yes, I forgot to do that. Done now.

changes ready for another look at dafd68e639a416fcae216c639c6e38beab53b214 on branch 16421-document-collection-deletion-lifecycle

LGTM