Skip to content
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

Docs: Internals: Data storage (Export archive) #4037

Closed
ramirezfranciscof opened this issue May 2, 2020 · 2 comments · Fixed by #4467
Closed

Docs: Internals: Data storage (Export archive) #4037

ramirezfranciscof opened this issue May 2, 2020 · 2 comments · Fixed by #4467

Comments

@ramirezfranciscof
Copy link
Member

No description provided.

@ramirezfranciscof ramirezfranciscof changed the title Docs - Data storage: Export archive Docs - Internals: Data storage (Export archive) May 2, 2020
@sphuber sphuber changed the title Docs - Internals: Data storage (Export archive) Docs: Internals: Data storage (Export archive) May 2, 2020
@csadorf csadorf added this to the Publish revised documentation milestone May 6, 2020
@csadorf csadorf removed this from the Publish revised documentation milestone May 15, 2020
@CasperWA CasperWA self-assigned this May 15, 2020
@ramirezfranciscof
Copy link
Member Author

Current link is broken.

Content should be on the old documentation.

@ltalirz
Copy link
Member

ltalirz commented Oct 19, 2020

To recap the discussion from the docs days wrap-up meeting:

We agree on the terms

  • "AiiDA archive format" for the format
  • "AiiDA archive files" or just "AiiDA archives" for the individual archive files

In particular, the term export is not needed to describe these files, but of course it remains useful to describe the process of creating them (one would say: "I export a subset of my graph to an AiiDA archive (file).").
The fact that the current AiiDA archive format contains a key export_version in the metadata.json is acceptable and does not need to be changed now (it could be changed in the new version of the archive format if desired).

We will try to avoid a nameclash with the upcoming new functionality for moving the outputs of CalcJobs to different storage locations (i.e. ideally not use the term "archive"/"archiving" there).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants