Closed mbjones closed 3 years ago
Here's the commits since v1.1.0 for determining committers.
git log --pretty=format:"%<(12)%as%Cred%<(10)%h%Creset%<(20)%an %s %Cblue%d" 1.1.0..develop
2021-01-27 0f545b5 Matt Jones Merge pull request #134 from ESIPFed/feature_72_provenance (HEAD -> develop, origin/feature_72_provenance, origin/feature-120-short-doi, origin/develop, feature_72_provenance, feature-120-short-doi)
2021-01-27 2bd9eb6 Matt Jones Incorporate `@id` into provenance statements to be LOD compliant.
2021-01-27 2d0db62 Matt Jones Merge branch 'develop' into feature_72_provenance
2021-01-25 3eb8508 Adam Shepherd Merge pull request #121 from ESIPFed/feature-120-short-doi
2021-01-21 fbd5b93 Matt Jones Updated provenace ADR to Accepted.
2021-01-21 7277168 Matt Jones Merge branch 'develop' into feature_72_provenance
2021-01-21 f58a750 Matt Jones Update cluster meeting info in Governance
2021-01-21 5f04958 Matt Jones Add cluster meeting info, and provide overview
2021-01-21 56304e1 Matt Jones Merge branch 'develop' into feature-120-short-doi
2021-01-21 ef40ae2 Matt Jones Add provenance example to full.jsonld.
2021-01-21 aad07b3 Matt Jones Merge branch 'develop' into feature_72_provenance
2021-01-21 7a2b21f Matt Jones Merge branch 'master' into develop
2021-01-06 544bd8b Stephen Richard ignore Oxygen project files (origin/master, origin/HEAD, master)
2020-11-11 7b12114 Douglas Fils Update full.jsonld
2020-11-05 b3d8389 Adam Shepherd Update Dataset.md
2020-11-05 0e092be Adam Shepherd add missing word for reason about page weight
2020-11-05 a667bca Adam Shepherd adds shortDOI URL using schema:sameAs property
2020-11-05 0b24f0d Adam Shepherd Adds a section to describe using shortDOI service
2020-11-02 461ca19 Matt Jones Restore HTML type to full JSON example.
2020-07-29 40343e0 Matt Jones Fix validation errors in example document.
2020-07-27 2464ef9 Matt Jones Add software workflow provenance section and diagram.
2020-07-27 48f6bfe Matt Jones Switch to SVG format for images.
2020-07-27 c8a9f1b Matt Jones Add initial figures for the provenance section to the Dataset guide.
2020-07-27 5c538fb Matt Jones Added section on `prov:wasDerivedFrom`.
2020-07-24 a11553a Matt Jones Inital Dataset Guide section and proposed ADR on providing provenance relationships.
2020-07-24 1f42d61 Matt Jones Merge branch 'develop' into feature_52_namespace_consistency (origin/feature_52_namespace_consistency, origin/Issue27-variableMeasured-PropertyID, feature_52_namespace_consistency, Issue27-variableMeasured-PropertyID)
2020-07-23 f033fef Dave Updated notebook example
2020-07-23 4adaad1 Dave Added an example in javascript for normalizing schema.org namespace
2020-07-21 150bbab Matt Jones Updated ADR with decision to use https namespace.
2020-07-17 9497cc8 Matt Jones Started branch and ADR for issue 52 on namespace consistency.
2020-04-01 da7ad05 datadavev Merge branch 'master' of https://github.com/ESIPFed/science-on-schema.org
2020-04-01 dfb367f Adam Shepherd remove dupe badges
2020-04-01 9d613ad Adam Shepherd update badges
2020-04-01 bb14af6 datadavev Merge branch 'master' of https://github.com/ESIPFed/science-on-schema.org
2020-04-01 44ee968 Adam Shepherd update broken links
2020-04-01 36fb96b Adam Shepherd Add Twitter follow
2020-04-01 031b1fd Adam Shepherd Update README.md
2020-04-01 e71fdd7 Adam Shepherd Update README.md
2020-04-01 a7da99e datadavev Merge branch 'upstream/master'
2020-03-24 c32ca87 datadavev Merge branch 'upstream/master'
2019-11-22 6ba054c Dave Vieglais Adjust ToC, added issue cross-reference
So that looks like Adam, Matt, Dave, Stephen, and Doug. @ashepherd Who else from issue discussions and calls should be added to the author list?
@mbjones thanks for kickstarting this!
I haven't gotten the reserve DOI at Zenodo to work. DOes anyone here know how to do that? If not, I'll just publish a minor revision to get that DOI into the README
@ashepherd Here's the instructions from the Zenodo help FAQ. I don't have write access to the product so I can't see if it works. But hopefully:
**Can I know the DOI of my record before publishing, so that I can include it in the paper or dataset?**
Yes you can! On the upload page under Basic Information and Digital Object Identifier click the Reserve DOI button. The text field above will display the DOI that your record will have once it is published. This will not register the DOI yet, nor will it publish your record (so you can still update the files). This DOI can be safely used in the record's own content as well as any other separate datasets or papers you might be planning to publish.```
ah ok! I had set it up to just publish a DOI everytime we made a new release, but I'll try this method instead.
Reserved DOI: 10.5281/zenodo.4477164
oh, so when we tag this will yet another DOI get issued that is different from the one you posted above?
@mbjones, no I turned off auto-publish for new github repo releases. All manual now, but we can still link to the Github Repo release page and use Datacite Relationships to relate them.
I updated the README with the new DOI and citation text. In addition to the authors listed above who authored new code and text in the commits listed, from a quick scan I found the following people contributed to the GitHub issue discussions, either via a suggestion or comments on a proposed approach:
Let's discuss the release citation for this tomorrow, and plan to update it as needed before posting to Zenodo.
FIXES
identifier
should be of type PropertyValue
sameAs
property is missingisAccessibleForFree
property is missingIMPROVEMENTS
schema:dateModified
for announcing when a Dataset resource has changed (Issue #67)
NEW FEATURES
Author List Matthew B. Jones, Steve Richard, Dave Vieglais, Adam Shepherd, Ruth Duerr, Mark Schildhauer, Nick Jarboe, Doug Fils
@ashepherd To contact for inclusion: Simon Cox, Adam Leadbetter, Alexandra Kokkinaki, Lewis McGibbney, Bryce Mecum, Thomas Thelen, Dan Brickley, Richard Wallis
Hi folks,
Science-on-Schema.org is preparing its latest release of schema.org publishing guidelines for describing science datasets and data repositories. We have identified that you have made contributions to this release through our Github issues. In publishing versions of our guidelines, we make all versions citable via Zenodo and wanted to ask for your permission to include you in the listing as one of this version's authors or contributors.
This is an 'opt-in' request. If you want to be included as an author/contributor, please respond back to this issue. Additionally, please specify your preference as author or contributor (we support you in whatever designation you prefer!). If applicable, you may also specify your ORCID identifier.
We plan to release the package on Friday, Monday 8 @ noon ET
Happy to get a name check as a contributor ~Richard.
Thanks @ashepherd. Happy with a contributor
acknowledgment on this - ORCiD 0000-0003-4382-2285
Thanks, happy to contribute. I had a look for an ORCiD for me last week and failed to find one. Seems like sort of thing I'd have signed up for but apparently not. So here you go, I finally got one: https://orcid.org/0000-0002-6450-7041
@danbri, great to have you participate in ESIP last week. thank you very much, and if there's anything we can do, let us know!
It was great to participate - let's take care to stay in touch :)
Final task list for preparing and releasing v1.2.
develop
develop
when all changes are merged todevelop
develop
intomaster
, tag release, publish to Zenodo