Currently, the following ID types are supported
The following prefix is used: 21.T11973
4 handles are prepared: 1 for ARKs, 1 for arXiv, 1 for SWHID and 1 for URN-NBN-DE, 1 for URN-NBN-FI and 1 for Zenodo ~
global proxy resolver to test everything: https://141.5.100.20:8000/
the global proxy http://hdl.handle.net/ also works
The landing page of a given pid could be requested if ?landingpage is added at the end of the pid or just only use the pid, for example 21.T11973/MR@urn:nbn:de:hbz:6-85659524771?landingpage
or 21.T11973/MR@urn:nbn:de:hbz:6-85659524771
Metadata record as far as offered by the respective providers could be requested if ?metadata is added at the end of the pid, for example 21.T11973/MR@urn:nbn:de:hbz:6-85659524771?metadata
Resource of the pid also as far as offered could be requested if ?resource is added at the end of the pid, for example 21.T11973/MR@urn:nbn:de:hbz:6-85659524771?resource
Put into the text field:
21.T11973/MR@ark:/13030/tf5p30086k
21.T11973/MR@arXiv:2302.00338
21.T11973/MR@swh:1:cnt:94a9ed024d3859793618152ea559a168bbcbb5e2
21.T11973/MR@urn:nbn:de:gbv:7-11858/00-1735-0000-002B-7D0C-3-1
21.T11973/MR@urn:nbn:fi-fe2021080942632
21.T11973/MR@10.5281/zenodo.8056361
Alternatively a pid example and a display type, including landingpage, metadata or resource, could be selected on ~~https://141.5.100.20:8000/ from the given test pids.
There is a resolution matrix on ~~https://141.5.100.20:8000/ which indicates the response types available for each given provider.