Comments on: Use cases for Handle identifiers? http://lackoftalent.org/michael/blog/2007/10/05/use-cases-for-handle-identifiers/ The occasional rambling of a digital library artisan Fri, 02 Dec 2011 10:37:42 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: mjgiarlo http://lackoftalent.org/michael/blog/2007/10/05/use-cases-for-handle-identifiers/comment-page-1/#comment-48683 mjgiarlo Fri, 05 Oct 2007 16:41:54 +0000 http://lackoftalent.org/michael/blog/2007/10/05/use-cases-for-handle-identifiers/#comment-48683 Aaron, Good point. Even local resources may be bound to URI schemes not of our choosing. The ideal solution would be if the software were configurable such that URIs could be crafted per organization policy. But I don't see that happening anytime soon. I'm not sure how much better option c is than option b since you're already running Apache (probably). Both are susceptible to the downstream citation problem which to my mind is a major knock on the persistence of an identifier. Apache + mod_proxy might be a better solution in terms of the problem, but I haven't wrapped my mind fully around the amount of management overhead that would be required in this scheme. Thanks for jogging my memory. And I do think Handles are a reasonable way to deal with the situation -- assuming the downstream citation problem is not an overriding issue. Aaron,

Good point. Even local resources may be bound to URI schemes not of our choosing. The ideal solution would be if the software were configurable such that URIs could be crafted per organization policy. But I don't see that happening anytime soon.

I'm not sure how much better option c is than option b since you're already running Apache (probably). Both are susceptible to the downstream citation problem which to my mind is a major knock on the persistence of an identifier. Apache + mod_proxy might be a better solution in terms of the problem, but I haven't wrapped my mind fully around the amount of management overhead that would be required in this scheme.

Thanks for jogging my memory. And I do think Handles are a reasonable way to deal with the situation — assuming the downstream citation problem is not an overriding issue.

]]> By: Aaron http://lackoftalent.org/michael/blog/2007/10/05/use-cases-for-handle-identifiers/comment-page-1/#comment-48680 Aaron Fri, 05 Oct 2007 12:17:28 +0000 http://lackoftalent.org/michael/blog/2007/10/05/use-cases-for-handle-identifiers/#comment-48680 Our organization runs multiple digital content / digital library publishing platforms, all with different URI schemes. In this case, the *resources* may be within our control, but the minting of URIs is not easy to get a handle on. It seems we are either faced with a) modifying the software to match a developed URI policy (ugh and/or not possible); b) running a translation scheme at the sever level (e.g. Apache mod_rewrite) (semi-ugh); or c) running some kind of resolver service, whether it be Handles or something else. In that accounting, Handles seem pretty reasonable to me -- what do you think? Our organization runs multiple digital content / digital library publishing platforms, all with different URI schemes. In this case, the *resources* may be within our control, but the minting of URIs is not easy to get a handle on.

It seems we are either faced with a) modifying the software to match a developed URI policy (ugh and/or not possible); b) running a translation scheme at the sever level (e.g. Apache mod_rewrite) (semi-ugh); or c) running some kind of resolver service, whether it be Handles or something else. In that accounting, Handles seem pretty reasonable to me — what do you think?

]]>