Comments (8)
I propose the one (or an updated version of) of what we have ATM
since it would provide a very nice and concise depiction of "actionable" functionality.
PS I think it is totally ok to have 2 or 3 figures
from datalad-paper-joss.
Ok, so here is an updated and extended version of this figure:
Key changes
- updated to reflect the current API
- de-emphasized the role of metadata, in particular its representation within a dataset
- give examples of extensions without going into details
from datalad-paper-joss.
nice! I would have liked to keep install
but I will not fight that.
can we still fit get
somewhere? IMHO it is more important than copy-file
from datalad-paper-joss.
@mih could you please upload .svg of this extended figure ? we are yet to add (or displace copy-file
) get
.
Actually save
should also get from External resources
, and that might be a good "section" for copy-file
if desired to keep it?
from datalad-paper-joss.
nice! I would have liked to keep
install
but I will not fight that.
Thx
can we still fit
get
somewhere? IMHO it is more important thancopy-file
We can replace copy-file
with get
from my POV.
@mih could you please upload .svg of this extended figure ? we are yet to add (or displace
copy-file
)get
.
Upload is done. I can edit later, once a conclusion is reached.
Actually
save
should also get fromExternal resources
, and that might be a good "section" forcopy-file
if desired to keep it?
I am not sure what you refer to with "save should also get from external". I placed it under "external" because it is the primary way to put non-datalad-racked content into datalad. There are a few exceptions, but in general this is the main entrypoint.
from datalad-paper-joss.
I am not sure what you refer to with "save should also get from external".
that it should not be listed among "External resources"
I placed it under "external" because it is the primary way to put non-datalad-racked content into datalad. There are a few exceptions, but in general this is the main entrypoint.
it is also the way to save
all local changes etc, unless we consider a "human operator mind" to be an "external resource". But if we do such a stretch, then all commands qualify "external resources" . Also since it operates on content in the tree (not some remote path, url etc) I feel that it is also a stretch for "external" in that aspect too. Even clone
is more "external" than save
in my mind. If we do want to keep separation from "External resources" and keep number of items, what about
- DataLad
- create
- clone
- run/rerun
- save
- External resources
- addurls
- get
But I think we might better just dissolve that difference (some group-vs-External resources) since that is the point somewhat to not care about that - datalad and git-annex help to make external resources look like "part of it", or keep it only for the right outgoing export-*
although even there it is already a bit of stretch since e.g. export-to-figshare annotates annex back with url to figshare. And hopefully eventually would do the same what datalad-osf
does by providing full git history etc.
Also update
on the right is odd since we are not pushing updates, we are fetching them, I would just remove it to avoid confusion. In the caption we should just say that it is just some of the commands, and refer to the cheatsheet for a more exhaustive list.
from datalad-paper-joss.
Sounds like the figure needs a major update, and I am not qualified to perform it.
from datalad-paper-joss.
Seems selection was made. I don't think it is worth keeping this particular issue open
from datalad-paper-joss.
Related Issues (20)
- It is annoying to get the draft.pdf from github actions -- use magic!
- Length of manuscript HOT 2
- Neuroscience focus yes|no? HOT 6
- Invitations (via github) to co-author a DataLad paper for JOSS HOT 4
- Substantial scholarly effort: prior citations HOT 3
- complete and harmonize affiliations HOT 3
- NeuroHub or CONP funding? HOT 4
- Invitations (via github) to co-author a DataLad paper for JOSS (last call) HOT 2
- Revise DataLad additions over git/git-annex section HOT 6
- Add section/paragraph on design principles HOT 1
- Primary demo HOT 5
- Reconsider "contributions" section HOT 1
- Paper structure/content HOT 4
- Complete acknowledgements HOT 2
- Add or purge metadata? HOT 2
- Stats on datasets.d.o HOT 2
- Fix date in YODA reference HOT 3
- Select title HOT 24
- Migrate into the datalad repository once the paper is ready HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from datalad-paper-joss.