museumpy is a client for python to get data from Zetcom MuseumPlus instances using its API.
museumpy is available on PyPI, so to install it simply use:
$ pip install museumpy
See the examples directory for more scripts.
importmuseumpyrecords=museumpy.search(
base_url='https://mpzurichrietberg.zetcom.com/MpWeb-mpZurichRietberg',
field='ObjObjectNumberTxt',
value='2019.184',
)
forrecordinrecords:
print(record)The return value of search is iterable, so you can easily loop over it. Or you can use indices to access elements, e.g. records[1] to get the second element, or records[-1] to get the last one.
Even slicing is supported, so you can do things like only iterate over the first 5 elements using
forrecordsinrecords[:5]:
print(record)importmuseumpyrecords=museumpy.fulltext_search(
base_url='https://test.zetcom.com/MpWeb-mpTest',
query='Patolu',
)
forrecordinrecords:
print(record)For more advanced usage of this library, it is recommened to first create a client instance and then use this to request data:
importmuseumpyimportrequestss=requests.Session()
s.auth= ('user', 'pass')
s.headers.update({'Accept-Language': 'de'})
client=museumpy.MuseumPlusClient(
base_url='https://test.zetcom.com/MpWeb-mpTest',
session=s
)importmuseumpyid='98977'module='Multimedia'item=client.module_item(id, module)importmuseumpyid='98977'module='Multimedia'# download attachment to a directory called `files`attachment_path=client.download_attachment(id, module, 'files')
print(attachment_path)There are most likely custom fields on the MuseumPlus Instance you want to query.
The returned XML is converted to a python dict using the xmltodict library.
The raw dict is returned on the raw key of the result:
importmuseumpyrecords=museumpy.search(
base_url='https://test.zetcom.com/MpWeb-mpTest',
query='Patolu',
)
forrecordinrecords:
print(record['raw'])For convenience a default mapping is provided to access some fields more easily:
forrecordinrecords:
print(record['hasAttachments'])
print(record['ObjObjectNumberTxt'])If you want to customize this mapping, you can pass a map_function to the client, which is then used on all subsequent calls to search and fulltext_search:
importmuseumpydefmy_custom_map(record, xml_rec):
NS="http://www.zetcom.com/ria/ws/module"ID_XPATH=f".//{{{NS}}}dataField[@name='ObjObjectNumberTxt']/{{{NS}}}value"TITLE_XPATH=f".//{{{NS}}}repeatableGroup[@name='ObjObjectTitleGrp']//{{{NS}}}dataField[@name='TitleTxt']//{{{NS}}}value"xml_parser=museumpy.xmlparse.XMLParser()
my_new_record= {
'my_id': xml_parser.find(xml_rec, ID_XPATH).text,
'my_title': xml_parser.find(xml_rec, TITLE_XPATH).text }
returnmy_new_recordclient=museumpy.MuseumPlusClient(
base_url='https://test.zetcom.com/MpWeb-mpTest',
map_function=my_custom_map,
)
records=client.search(
base_url='https://test.zetcom.com/MpWeb-mpTest',
query='Patolu',
)
forrecordinrecords:
print(record['my_id'])
print(record['my_title'])To create a new release, follow these steps (please respect Semantic Versioning):
- Adapt the version number in
museumpy/__init__.py - Update the CHANGELOG with the version
- Create a pull request to merge
developintomain(make sure the tests pass!) - Create a new release/tag on GitHub (on the main branch)
- The publication on PyPI happens via GitHub Actions on every tagged commit