Each institution is responsible for arranging their own handles, and must inform VTLS of the details. VTLS does not organise the handles on behalf of the client. There was originally a preference for ARROW branded handles. The details of this thinking may be found at | HandlesPersistentIdentifiers

The current situation is this:

ARROW uses the handles system offered by the | Corporation for National Research Intitiatives (CNRI) for assigning, managing and resolving persistent identifiers for all its digital objects.

The CNRI Handles system was chosen over the Digital Object Identifier (DOI) scheme because it is available at no cost for research use.

CNRI has allocated the ARROW project the generic naming authority number of 1959, which is then followed by a running ID for each institution, as in 1959.1.

Early in ARROW’s development the handle format was agreed to be a branded ARROW format. Monash University, for example, uses the format http://arrow.monash.edu.au/hdl/1959.1/2658. University of NSW also uses the ARROW branded format, as in http://arrow.unsw.edu.au/hdl/1959.4/545.

ARROW branding is not mandatory. Swinburne University, for example, uses a non-branded format - http://hdl.handle.net/1959.3/2394. A consequence of there decision is that resolution of their handles is also done by CNRI in the USA and not locally and so they have a dependency on this service into the future.

Each new institution is responsible for requesting registration of its running number with CNRI. Email mailto:hdladmin@cnri.reston.va.us to request your naming authority. Make sure you specify that you are part of the ARROW project, and expect your handle to be 1959.n.

Each institution must arrange its own handles server before installation of the VITAL software can be done. VTLS requires information about your Handles Server Port, the Handles Server Port, the Handles Server Web Port, and the Handles Naming Authority before VITAL can be installed and configured. The Handles registration may be done through VTLS, but they will charge a separate fee for it.

The handles software and further information is available at [http://www.handle.net/introduction.html].

The readme from the handles software is attached below.

Simon Huggard from Monash University has written a procedure for installation and configuration…
''After many installs on various servers here at Monash, we've had a lot of experience in getting handles servers to work. We found one very odd thing you can try to see if it fixes the problem or not. If you "Home" your handles server using the handles.jar tool itself, this may fix it. We found on one of our servers that the diagnostics page said it was successfully able to create test handles, but it still wouldn't actually create real ones. So by using the handles tool to "home" the server, for some reason it fixed it.

Attached is our installation and configuration procedure. If you look at point 4 on page 7, it tells you how to do this. I would suggest you give that a try, but it may not work for you, particularly if your network or your server is configured to block UDP traffic via port 2641 that the handles software uses (we had this trouble with one of our servers that required a fix on either the firewall or the server — we weren't actually told what our central IT services people changed). Naturally you would also have to copy your admpriv.bin file from your server, down to your PC in order to be able to authenticate to the handles server from your PC. The instructions cover all of these points.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License