Archive.org backup set should include more context

[science]

We backup data files using mime-encoded "json lines"
We should also backup:

• Instructions on how the files were created - a "readme"
• Schemas that describe the json that was backed up

dump- ==> backups
readme- ==> instructions on how to use the file

Here https://sandbox.credentialengineregistry.org/, under every community add a 'json' node defining whether the community is private or not.

[siuc-nate]

What is the status of all archive.org related implementation issues/details?

[rsaksida]

If I understood this issue correctly, the idea is that the backup files would have some additional info embedded with them. Like a README inside the zip file that is uploaded into archive.org. That hasn't been implemented.

[edgarf]

Additional reference: #221

[siuc-nate]

Per our 2024-05-13 meeting:

• We will come up with text to go in a readme file along with the archive.org backups (not @excelsior - @edgarf @science to talk and figure out who will do this)
• We will continue daily differential backups (no change)
• We will add periodic full backups (either monthly or yearly)
• @excelsior will add an indicator to the community metadata API endpoint that indicates whether or not that community is being backed up