diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-edc-metadata.spec | 85 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 87 insertions, 0 deletions
@@ -0,0 +1 @@ +/edc-metadata-0.3.51.tar.gz diff --git a/python-edc-metadata.spec b/python-edc-metadata.spec new file mode 100644 index 0000000..0de5712 --- /dev/null +++ b/python-edc-metadata.spec @@ -0,0 +1,85 @@ +%global _empty_manifest_terminate_build 0 +Name: python-edc-metadata +Version: 0.3.51 +Release: 1 +Summary: Add a metadata layer to data entry +License: GPL license, see LICENSE +URL: https://github.com/clinicedc/edc-metadata +Source0: https://mirrors.aliyun.com/pypi/web/packages/1c/d8/cf085de77b4e0ac4841b9becc7024fb0410f592c1c555a2311e5e19573b5/edc-metadata-0.3.51.tar.gz +BuildArch: noarch + +Requires: python3-tqdm + +%description +``edc-metadata`` puts a "metadata" layer on top of your data collection forms, namely CRFs and Requisitions. The "metadata" is used on the data entry dashboard (see also `edc_dashboard`). The metadata may be queried directly by a data manager to review the completion status of CRF and Requisition forms. +* Metadata is stored in two models, ``CrfMetaData`` and ``RequisitionMetaData``. One metadata record is created per form per visit. Metadata is only created for the data collection forms of a visit as defined in the ``visit schedule``. +* Metadata model instances are created for each visit when the ``visit`` model is saved. ``edc_metadata`` reads from the ``visit_schedule`` to decide which data collection form metadata model instances to create for a visit. (Note: See ``edc_visit_schedule``) +* Metadata is guaranteed to exist for every form defined in a visit after the visit form has been submitted. + Note: This module is coupled with ``edc_metadata_files`` and ``edc_reference``. + +%package -n python3-edc-metadata +Summary: Add a metadata layer to data entry +Provides: python-edc-metadata +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-edc-metadata +``edc-metadata`` puts a "metadata" layer on top of your data collection forms, namely CRFs and Requisitions. The "metadata" is used on the data entry dashboard (see also `edc_dashboard`). The metadata may be queried directly by a data manager to review the completion status of CRF and Requisition forms. +* Metadata is stored in two models, ``CrfMetaData`` and ``RequisitionMetaData``. One metadata record is created per form per visit. Metadata is only created for the data collection forms of a visit as defined in the ``visit schedule``. +* Metadata model instances are created for each visit when the ``visit`` model is saved. ``edc_metadata`` reads from the ``visit_schedule`` to decide which data collection form metadata model instances to create for a visit. (Note: See ``edc_visit_schedule``) +* Metadata is guaranteed to exist for every form defined in a visit after the visit form has been submitted. + Note: This module is coupled with ``edc_metadata_files`` and ``edc_reference``. + +%package help +Summary: Development documents and examples for edc-metadata +Provides: python3-edc-metadata-doc +%description help +``edc-metadata`` puts a "metadata" layer on top of your data collection forms, namely CRFs and Requisitions. The "metadata" is used on the data entry dashboard (see also `edc_dashboard`). The metadata may be queried directly by a data manager to review the completion status of CRF and Requisition forms. +* Metadata is stored in two models, ``CrfMetaData`` and ``RequisitionMetaData``. One metadata record is created per form per visit. Metadata is only created for the data collection forms of a visit as defined in the ``visit schedule``. +* Metadata model instances are created for each visit when the ``visit`` model is saved. ``edc_metadata`` reads from the ``visit_schedule`` to decide which data collection form metadata model instances to create for a visit. (Note: See ``edc_visit_schedule``) +* Metadata is guaranteed to exist for every form defined in a visit after the visit form has been submitted. + Note: This module is coupled with ``edc_metadata_files`` and ``edc_reference``. + +%prep +%autosetup -n edc-metadata-0.3.51 + +%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-edc-metadata -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Thu Jun 08 2023 Python_Bot <Python_Bot@openeuler.org> - 0.3.51-1 +- Package Spec generated @@ -0,0 +1 @@ +1ac2f19aad055a577d90424ab4b6531f edc-metadata-0.3.51.tar.gz |