link to annex web application for EAF files

[dietuyt]

For EAF ResourceProxy?'s (mimetype="text/x-eaf+xml") the link in the VLO should point to the Annex viewer instead of the plain XML

E.g. for ​http://catalog.clarin.eu/ds/vlo/?wicket:bookmarkablePage=:eu.clarin.cmdi.vlo.pages.ShowResultPage&fq=language:Bulgarian&docId=test-hdl:1839/00-0000-0000-0014-FABE-B

The VLO now links to the XML representation of the EAF:

​http://hdl.handle.net/1839/00-0000-0000-0014-FAC0-4

This should become:

​http://corpus1.mpi.nl/ds/annex/runLoader?handle=1839/00-0000-0000-0014-FAC0-4

[herste]

Is there a way to distinguish between EAF handle links and other handle links?

[dietuyt]

Yes, there are 2 options:

• looking at the mimetype attribute (as mentioned in this ticket)
• using the handle API, but then ticket:136 needs to be fixed first

[larlam]

Replying to herste:

Is there a way to distinguish between EAF handle links and other handle links?

You can look at the mime type, e.g.

<ResourceProxy id="d203465e1156">

<ResourceType mimetype="text/x-eaf+xml">Resource</ResourceType?>
<ResourceRef>hdl:1839/00-0000-0000-0014-FAC0-4</ResourceRef?>

</ResourceProxy?>

[larlam]

Damn, Dieter's reply only became visible after I typed mine. This thing should have an auto-refresh.

[teckart]

Is there any news about the handle parameter for the Annex webviewer?

[larlam]

Annex has supported the handle parameter for quite some time now, so there shouldn't be anything external left blocking this feature from being enabled in VLO.

[larlam]

BTW, it would probably help progress if the current VLO maintainer was actually on this ticket.

[Twan Goosen]

Kees Jan no longer works on VLO. Assigning all VLO web app tickets owned by KJ to Twan

[herold@bbaw.de]

Isn't this a client side problem? PID should be handled all the same, regardless of what they are pointing at (or rather of what the metadata description claims they are pointing at), no?

[Twan Goosen]

I agree with Axel's comment. A possible solution would be to provide 'raw' and 'view' links for each resources (maybe in an extended resources view, e.g. a table). Some convention has to be used for this though, e.g. appending the "@view" part identifier to the handle (which needs to be supported by the handle server).

If there is consensus about this, replace this with a new and more targeted ticket?

Also see #213

[herold@bbaw.de]

Twan, that'd be fine with me. Let's give others a few days to comment, though.