Imported from previous forum
On the above page, when a user is not logged in they see three options at the very bottom of the page. But when user is logged in they see the additional option of the "Codelists" option.
1) how can we show the "Codelist" option similar to the specs where we like the user to see that option exists but they must login to get access to the files.
2) I am trying to understand why clicking on "Codelist" itself can't take me directly to the files? Why must the "Visit source" be clicked on. I find this a bit counter-intuitive. Clicking on "Codelist" takes me to some other landing page that I feel is not necessary and the text content on that page can be on the same page as where the files are (which it already is).
Hi Lisa,
1. The list of links you see in this page are constructed using ECML and the bookmarks feature. Each Bookmark has its own access control setting and the reason why the 'Codelist' link was invisible to the Public was because the Access Control in that case was set to 'Logged in Users only'. I have corrected this by editing the bookmark and the link is now visible to everyone.
On the Codelist page itself, each of the files has it's own Access Control setting which is currently 'Logged in Users only' - this means it is only visible to logged in users. In other sections of the site (such as http://www.fixtradingcommunity.org/pg/structure/tech-specs/fix-version/50-service-pack-2) we have used the text '(only visible to logged-in users)' to indicate that a user must be logged in to view a list like this.
It is extremely easy to the edit the block at http://www.fixtradingcommunity.org/pg/structure/tech-specs/extension-pack-supplements/codelists - if you wish to include this text.
The only other way it is possible to do this is to apply a licence to the individual documents. That way, you can make the document public but any user attempting to access it would need to accept a licence which would only be accessible to logged in users. This is a useful feature generally but rather fiddly to set up, and probably not appropriate for this kind of content, as it would require several more steps before the content became available to users who were already logged in.
2. With respect to the 'visit resource' question. This is actually a feature of the Bookmark 'View type' generally. It would be possible to create a new view type whoch would get around the issue however doing so is technically demanding in terms of time, and would need to be added to Jira as a 'feature request' and be subject to prioritisation by the program office.
The simplest way to avoid the issue is to dispense with the use of ECML and bookmarks here entirely. There is nothing to stop you editing the block at http://www.fixtradingcommunity.org/pg/structure/tech-specs/fix-protocol - removing the ECML and replacing it with plain html links to the pages in question. The upside here is that you remove any confusion associated with the bookmark view-type, the downside is that you lose some consistency in the page-formatting and maintaining the block becomes a manual process.