We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Goal: Implement get-record CLI function to fetch some wanted record metadata.
get-record
Inputs: --recid or --doi ot --title (useful for CMS datasets). One of them should be required.
--recid
--doi
--title
Outputs: Full JSON of the bibliographic record.
Optionally, if some CLI switch is used, output only that JSON subtree.
Examples:
$ cernopendata-client get-record --recid 14 $ cernopendata-client get-record --doi 10.7483/OPENDATA.ATLAS.AHKR.A3TA $ cernopendata-client get-record --recid 14 --output-fields title,date_created $ cernopendata-client get-record --tile '/Mu/Run2010B-v1/RAW' --output-fields recid
Exit status: 0 if OK, 1 if more then one record was matched. (Should not happen.)
The text was updated successfully, but these errors were encountered:
cli: add get-record command
16724f2
* Closes cernopendata#2 * refactor some code
docs: initialize sphinx documentation
0b2d584
* Addresses cernopendata#1 * add docs for get-record command (Addresses cernopendata#2) Signed-off-by: Jan Okraska <jan.okraska@cern.ch>
db86caa
okraskaj
No branches or pull requests
Goal: Implement
get-record
CLI function to fetch some wanted record metadata.Inputs:
--recid
or--doi
ot--title
(useful for CMS datasets). One of them should be required.Outputs: Full JSON of the bibliographic record.
Optionally, if some CLI switch is used, output only that JSON subtree.
Examples:
Exit status: 0 if OK, 1 if more then one record was matched. (Should not happen.)
The text was updated successfully, but these errors were encountered: