Add function to publish EML data through Github about eml HOT 7 CLOSED

Although, we could make an R interface to git...

from eml.

@schamberlain How would you do that? I wondered that too at Scifoo where I met the creator of Authorea. We talked about a ropensci interface to Authorea but ultimately it boils down to a git interface.

from eml.

Hmm, not sure, wil think about it

On Tuesday, June 25, 2013, Karthik Ram wrote:

@schamberlain https://github.com/SChamberlain How would you do that? I
wondered that too at Scifoo where I met the creator of Authoreahttps://www.authorea.com/.
We talked about a ropensci interface to Authorea but ultimately it boils
down to a git interface.

—
Reply to this email directly or view it on GitHubhttps://github.com/ropensci/reml/issues/4#issuecomment-20029787
.

from eml.

One might start with an RCurl implementation of the Github API. That would provide data for things of interest (commits, issues, activity, org, users, etc) http://developer.github.com/v3/

For git commands though you might be stuck with wrapping system calls (and possibly having to parse their return text from intern=TRUE). Perhaps that could be adequate. It would allow something like eml_publish(..., dest=github) but I'm not sure if that would actually be useful. I'd want a function to write the URL endpoints into the EML but I might rather push myself...

from eml.

I have some functions I already wrote to do that blog post on github stats on our repos - functions are in the ropensci::sandbox repo. Looks like you can actually create commits via the API, and perhaps push, though not positive about that.

from eml.

Okay, fixed user-agent string now required, just a few functions in the sandbox repo: https://github.com/ropensci/sandbox

Should probably make a separate repo for github...

from eml.

Not sure that it makes sense to have a publish("file.xml", repo="github") in the same sense as publish("file.xml", repo="KNB") or publish("file.xml", repo="figshare"). Github isn't indexed in the same way as these data repositories -- not clear where the data would be published to on Github anyway.

In particular, the other repositories have their own notion of metadata, so it makes sense to have a function that can map EML metadata into, say, the required figshare title, category, tag, author, and description boxes. The same is not true for Github. Users can always use eml_write and put their EML where-ever they want.

from eml.