Vocabular URI and broken links

[ttjelta]

Using a vocubulary URI (as entered in the Vocabulary configuration form) other than the actual host/path URL of our tematres instance causes a problem with certain links.

E.g. our tematres instance is to be found at http://myhost.mysite.no/tematres/vocab/ but we want the vocabulary URI to be independant of this, e.g. http://my.id.no/vocab

In two cases the vocabulary URI occurs in (invalid) links within the application: • The hierarchical representation of the vocabulary on the home page. (Navigation arrows works, but all concept links are dead.) • On successful login, there is a redirect to the vocabulary URI, not to tematres.

All other links seems to works perfectly, e.g. using search or alphabetic navigation.

We have found minimal ad hoc fixes for the two cases, by making the relevant link URLs relative:

In common/include/fun.html.php (1949)

• • $urlTerm=$url_parts['scheme'] . '://' . $url_parts['host'] . ':' . $url_parts['port'] . $url_parts['path'].'index.php?tema='.$arrayTerm["tema_id"].'&/'.string2url($arrayTerm["tema"]);
• • $urlTerm='index.php?tema='.$arrayTerm["tema_id"].'&/'.string2url($arrayTerm["tema"]);

In common/include/session.php (106)

• • header("Location: " . $_SESSION["CFGURL"].$add_param);
• • header("Location: " .$add_param);

This mends the observed issues, but we have not done extensive testing, and we are not certain whether this is a sustainable solution.

[tematres]

Hi dear @ttjelta :) thank you about the feed back. Before all, please be patient with my english :/ We adopt this policy because the URL base of the vocabulary is part of the metadata exposed about the vocabulary, and if the declared URL base is not a valid URL can create future interoperability problems. You can change the URL base in Config form (Menu -> Administration -> Config). Anyway... there are other users who was (negative) comments about this policy.... may be we need to change it and use relative URL. what do you tihnk?

[ttjelta]

Thank you for your answer! Our use case is that we want to apply TemaTres for creating and editing our vocabularies, and then export the vocabularies to a different system for publication. Thus we need vocabulary and term URIs independant of our local tematres url. We therefore think it would be better if the base URI of a vocabulary did not affect the internal navigation within the system, as in the two cases mentioned above. We lack the overview of TemaTres to judge what is the appropriate action, and we may of course keep to making local ajustments, unless our use case is relevant to other users as well?