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.

Sign up for GitHub

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

Jump to bottom

create a mechanism for inspecting Artifacts #24

Closed
gregcaporaso opened this issue Mar 10, 2016 · 0 comments
Closed

create a mechanism for inspecting Artifacts #24

gregcaporaso opened this issue Mar 10, 2016 · 0 comments
Assignees
@jairideout

Comments

@gregcaporaso
Copy link
Member

Likely as a method of Artifact, or some way to view properties of it from interfaces. We need to think about what this would be exactly, but we need some way to view provenance, view summaries of the underlying data, etc.
@jairideout jairideout self-assigned this Jul 6, 2016
jairideout added a commit to jairideout/qiime2 that referenced this issue Jul 6, 2016
@jairideout
ENH/BUG: add Artifact/Visualization.peek for quick inspection of arch…
8e6de41 
…ives

Solves bug in Artifact/Visualization.load where previously the archive filepath was extracted on demand, resulting in buggy behavior if the filepath was deleted or modified after loading but prior to extraction. This problem is not easily solvable in a cross-platform compatible way so a new `.peek()` classmethod is provided to quickly retrieve an archive's metadata (e.g. UUID, type, and provenance) without extracting. `.load()` now extracts immediately.

Fixes qiime2#24.
@jairideout jairideout mentioned this issue Jul 6, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jairideout jairideout

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gregcaporaso @jairideout