%global _empty_manifest_terminate_build 0 Name: python-caltechdata-api Version: 1.4.1 Release: 1 Summary: Python wrapper for CaltechDATA API. License: https://data.caltech.edu/license URL: https://github.com/caltechlibrary/caltechdata_api Source0: https://mirrors.aliyun.com/pypi/web/packages/02/ff/a1ce155609305fff701d2d415132d6b99fd5be3c3095b103eb2741194cd4/caltechdata_api-1.4.1.tar.gz BuildArch: noarch Requires: python3-requests Requires: python3-datacite Requires: python3-tqdm Requires: python3-pyyaml Requires: python3-s3fs %description # caltechdata_api Python library for using the CaltechDATA API - caltechdata_write write files and a DataCite 4 standard json record to CaltechDATA repository - caltechdata_edit edits records in CaltechDATA - get_metadata gets metadata from CaltechDATA records Requires Python 3 (Recommended via Anaconda https://www.anaconda.com/download) with reqests library. ## Examples There are some example python scripts in the GitHub repository. Create a record: ```shell python write.py example.json -fnames logo.gif pbkn6-m9y63 ``` The response will be the unique identifier for the record. You can put this at the end of a url to visit the record (e.g. https://data.caltechlibrary.dev/records/pbkn6-m9y63) Edit a record (make changes to the example.json file to see a change) ``` python edit.py example.json -id pbkn6-m9y63 10.33569/pbkn6-m9y63 ``` The response is the DOI for the record, which includes the unique identifier for the record in the default configuration. Some groups have worked with the library to create custom DOIs. These can be passed in the metadata like: ```shell python write.py example_custom.json -fnames logo.gif m6zxz-p4j22 ``` And then you can edit with ``` python edit.py example_custom.json -id m6zxz-p4j22 10.5281/inveniordm.1234 ``` This returns the custom DOI of the record if it is successful. ## Setup Install by typing 'pip install caltechdata_api' ## Usage You need to acquire a personal access token from your CaltechDATA account (find it at the top right of your screen under "Applications"). Then copy the token to token.bash. Type `source token.bash` in the command line to load the token. Only test your application on the test repository (data.caltechlibrary.dev). Testing the API on the public repository will generate junk records that are annoying to delete. %package -n python3-caltechdata-api Summary: Python wrapper for CaltechDATA API. Provides: python-caltechdata-api BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-caltechdata-api # caltechdata_api Python library for using the CaltechDATA API - caltechdata_write write files and a DataCite 4 standard json record to CaltechDATA repository - caltechdata_edit edits records in CaltechDATA - get_metadata gets metadata from CaltechDATA records Requires Python 3 (Recommended via Anaconda https://www.anaconda.com/download) with reqests library. ## Examples There are some example python scripts in the GitHub repository. Create a record: ```shell python write.py example.json -fnames logo.gif pbkn6-m9y63 ``` The response will be the unique identifier for the record. You can put this at the end of a url to visit the record (e.g. https://data.caltechlibrary.dev/records/pbkn6-m9y63) Edit a record (make changes to the example.json file to see a change) ``` python edit.py example.json -id pbkn6-m9y63 10.33569/pbkn6-m9y63 ``` The response is the DOI for the record, which includes the unique identifier for the record in the default configuration. Some groups have worked with the library to create custom DOIs. These can be passed in the metadata like: ```shell python write.py example_custom.json -fnames logo.gif m6zxz-p4j22 ``` And then you can edit with ``` python edit.py example_custom.json -id m6zxz-p4j22 10.5281/inveniordm.1234 ``` This returns the custom DOI of the record if it is successful. ## Setup Install by typing 'pip install caltechdata_api' ## Usage You need to acquire a personal access token from your CaltechDATA account (find it at the top right of your screen under "Applications"). Then copy the token to token.bash. Type `source token.bash` in the command line to load the token. Only test your application on the test repository (data.caltechlibrary.dev). Testing the API on the public repository will generate junk records that are annoying to delete. %package help Summary: Development documents and examples for caltechdata-api Provides: python3-caltechdata-api-doc %description help # caltechdata_api Python library for using the CaltechDATA API - caltechdata_write write files and a DataCite 4 standard json record to CaltechDATA repository - caltechdata_edit edits records in CaltechDATA - get_metadata gets metadata from CaltechDATA records Requires Python 3 (Recommended via Anaconda https://www.anaconda.com/download) with reqests library. ## Examples There are some example python scripts in the GitHub repository. Create a record: ```shell python write.py example.json -fnames logo.gif pbkn6-m9y63 ``` The response will be the unique identifier for the record. You can put this at the end of a url to visit the record (e.g. https://data.caltechlibrary.dev/records/pbkn6-m9y63) Edit a record (make changes to the example.json file to see a change) ``` python edit.py example.json -id pbkn6-m9y63 10.33569/pbkn6-m9y63 ``` The response is the DOI for the record, which includes the unique identifier for the record in the default configuration. Some groups have worked with the library to create custom DOIs. These can be passed in the metadata like: ```shell python write.py example_custom.json -fnames logo.gif m6zxz-p4j22 ``` And then you can edit with ``` python edit.py example_custom.json -id m6zxz-p4j22 10.5281/inveniordm.1234 ``` This returns the custom DOI of the record if it is successful. ## Setup Install by typing 'pip install caltechdata_api' ## Usage You need to acquire a personal access token from your CaltechDATA account (find it at the top right of your screen under "Applications"). Then copy the token to token.bash. Type `source token.bash` in the command line to load the token. Only test your application on the test repository (data.caltechlibrary.dev). Testing the API on the public repository will generate junk records that are annoying to delete. %prep %autosetup -n caltechdata_api-1.4.1 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "\"/%h/%f.gz\"\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-caltechdata-api -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Tue Jun 20 2023 Python_Bot - 1.4.1-1 - Package Spec generated