Closed rmflight closed 10 years ago
Currently only the form that collects information from the repository is available for testing, to get feedback on whether all the information that's useful to have associated with a code archive is being collected. The figshare endpoint for actually archiving the repository and generating a DOI will be available soon…
Ah, OK, I misunderstood the email then. The bookmarklet is a prototype of what the submission would look like, and does this appear to be what should be required for submission to get a DOI then. That makes sense.
Essentially, yes. The bookmarklet is also a prototype of a workflow that starts in the GitHub repository, makes sure all the required information is present (and potentially offers feedback on how to improve the metadata in the repository), then allows the user to choose which service to use to archive the code.
I hadn't had a chance to play with the prototype until now, but did anyone else get a 404 error message from Figshare after hitting submit?