URLs / links should use persistent identifiers (Handles) instead of internal IDs

[tdonohue]

Instead of URLs / paths like: http://ui-prototype.atmire.com/items/86514

We should be using paths based on persistent identifiers (e.g. Handles). So, in the above example, the underlying object's handle is http://hdl.handle.net/1969.1/86172

Therefore, its URL should be something like: http://ui-prototype.atmire.com/handle/1969.1/86172

[artlowel]

I don't entirely agree. We should also support handles, as persistent identifiers, but I still think we should retain REST-ful URLs as they make it more clear what to expect. We should be able to add a handle route, that redirects to the correct page.

We can still use the handle URL in tags and add a "persistent URI" metadata field to the item pages with the handle URL.

[tdonohue]

Hi @artlowel... I see your point.

It would be a different behavior for DSpace (which tends to use /handle paths heavily). But, there are advantages to that approach (e.g. we could have routes for other persistent identifiers that can redirect you to the right place, as needed). At the same time, this sounds like something we'd want to discuss more broadly to ensure DCAT and Committers agreed as well.

So, for now, I like your suggestion. Let's simply put in a 'handle' route that redirects the user to the proper page, etc. Then we can use that as a way to kick off this discussion with others.