...
- After the protocol (http://) and host (cul.cornell.edu) sections, PURLs have a domain component of arbitrary length (e.g., /net/example), followed then by the local identifier. The software is set up to allow the specification of users allowed to create or maintain domains; if nesting domains are set up (e.g., http://cul.cornell.edu/abc/12345
and http://cul.cornell.edu/abc/def/12345), how does the software avoid conflicts over administration rights for /abc vs. /abc/def? Apparently via exact string matching; there's no notion of the /abc/def domain having any relationship to the /abc domain.
Comments
- The application has a functional and attractive interface; we were each able to create user accounts and then make domains and PURLs using those domains; the few PURLs we created interactively worked correctly.
- However, establishing a domain seems to be flaky – a number of domains were established without warning or error messages, but could not then be used to create PURLs and could not be found through the domain search tool, which reported "Search Successful" but "No Results". An option to list domains and their attributes would be very helpful
...