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

Notebook or Labbook for datasets #2210

Closed
mercecrosas opened this issue May 28, 2015 · 7 comments
Closed

Notebook or Labbook for datasets #2210

mercecrosas opened this issue May 28, 2015 · 7 comments

Comments

@mercecrosas
Copy link
Member

A suggestion from Dustin Tingley (also requested by other users from different scientific domains):

Connect a dataset with a labbook or notebook, or more generally a documentation stream that a researcher produces that documents semi-regularly issues that come up in the research process.

This could be implemented by having a metadata field in the dataset that points to the labbook. It could integrate either with labbok.org or ipython notebook.

@mercecrosas mercecrosas self-assigned this May 28, 2015
@mercecrosas mercecrosas added this to the In Review milestone May 28, 2015
@tingleyd
Copy link

For the persistence issue you point to in your email Merce, my idea there was that DV would just query the text contents of the link so it would be stored on DV side. This was just to make it simple for users to update regularly, but have those updates stored within a DV log. But, if there is an ipython way that would be most robust and get you additional features, that is cool.

My primary concern here is it has to be hyper easy (as G points to too), Hence, having single sign on type setup for labbook.org. This doesn't exist as a domain name yet but could, allowing you ways to let people use the site for writing their labbook, and then encourage them to setup a DV study so it logs their progress. This may habitualize them to subsequently post their replication data, or use other DV features.....

dt

@pdurbin
Copy link
Member

pdurbin commented May 31, 2015

Since IPython Notebook has been mentioned I'd be remiss if I didn't link to the conversation with @fperez over at IQSS/dataverse-client-python#6

What's interesting is that what @tingleyd seems to be describing sounds like Dataverse would pull (query) some other system for updates. This sounds a bit like harvesting (#813) or maybe ResourceSync or SHARE (both mentioned in #900). Anyway, I'm curious what the mechanism or protocol would end up being. (The remote lab notebook could always push data into Dataverse via SWORD if it knows that protocol.)

I'm also curious to hear more about what is being proposed for single sign on. It sounds like good fodder for discussion in the Dataverse Auth Community Group. :)

@tingleyd
Copy link

Curious whether this idea is making any progress.

@mercecrosas
Copy link
Member Author

@tingleyd no progress yet, but will be reviewed soon - @eaquigley and @scolapasta are going through the backlog of issues to prioritize. The process will be to first define well the requirements and come up with a proposal to review.

@scolapasta scolapasta removed this from the Not Assigned to a Release milestone Jan 28, 2016
@pdurbin
Copy link
Member

pdurbin commented Jun 25, 2017

@tingleyd RSpace ( https://www.researchspace.com ) is an electronic lab notebook that now integrates with Dataverse:

Is that enough to close this issue? If not, should we make it more specific? We're trying to work in smaller chunks these days.

@tingleyd
Copy link

tingleyd commented Jun 25, 2017 via email

@pdurbin pdurbin removed the Triaged label Jun 25, 2017
@pdurbin
Copy link
Member

pdurbin commented Jun 25, 2017

@tingleyd thanks for getting back to me so quickly! Since this issue was originally added based on your suggestion, I'm going to close it out but others watching this issue who are interested in specific integrations with software other than RSpace should open a fresh issue mentioning the tool in question. Thanks!

@pdurbin pdurbin closed this as completed Jun 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants