-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Finalize export metadata format #280
Comments
It may be worth comparing this approach with the ZIP folder structure generated by downloads from the Journalist Interface, which looks like this:
The date used for the folders is the "last updated" date for a given source (https://github.com/freedomofpress/securedrop/blob/develop/securedrop/store.py#L137). |
See also the related issue of handling filename conflicts: #270 |
A draft of the metadata archive format specification can be found in the following document https://docs.google.com/document/d/1qoQMMGjB9d9mHelZg_lncgiMjjB1BxIvZot_2Y6KjqM for discussion as part of the 7/24-8/7 sprint. |
@emkll I gave the google doc a first pass review and left a few comments and some suggestions. |
also dropped some comments inline, otherwise LGTM! |
Thanks @creviera and @redshiftzero for the comments/suggestions, they have all been addressed/accepted, and they should now be consistent with the changes in freedomofpress/securedrop-export#5 . I think this should now be sufficient to close the ticket. If anyone disagrees, please feel free to repoen/comment. |
#259 implemented a basic, manual export workflow and specified (in the README) a metadata format for exports:
metadata.json example:
Before we implement export support in the client (freedomofpress/securedrop-client#21) we should be sure that this is the format specification we want to go with. For example, is there other information we want to include in the metadata or folder structure (e.g., source name, date/time of export)?
The text was updated successfully, but these errors were encountered: