Keyword as Links

Hi everyone,

I have seen other people have wished for linked keywords before. However, it seems the issue has been linked and closed in the respective github issue. The milestones for OJS3.2 say that you are planning on implementing browsing of keywords, but not actually the linking of the keywords as clickable tags.
For us this is a very important feature and I would like to suggest you include it again.
Readers and authors are used to having keywords that refer to a list other documents that use the same keywords. This feature would add significantly to the usability of the OJS frontend.


Hi @fpannach, I think it is suggested in the issue you cite.
At least, this issue was closed just for that reason:

Hi @Ph_We,
thanks for the quick reply. As far as I can tell the issue was closed because

I think what you want is browsing by subject/keyword,

which is not the full nature of the request, because the milestones do not include the linking part anymore, only the searchability itself.


It’s not easy to conceive any other ‘browsing by keywords’, than browsing by those displayed as ‘tags’ on the article page. However, I’d rather ask @NateWr what he might have meant :slight_smile:

The original wording was:

Could we make those keywords linked, taking the reader to the search results page for that keyword?

nothing about the browsing.

Have you looked at the GitHub - ali-sokhandan/ojs3-keywordcloud-plugin: A block plugin to provide a tag cloud of article keywords. - it does what you want.

You can see it in action here:

That plugin is not supported anymore (it isn’t compatible with 3.1.2.*). Anyway, I believe @fpannach would like those keywords (tags), which are listed on the article page, to be displayed as linked ones (clickable).

Wrong. I made it compatible with OJS 3.1.2 . The example I gave runs on OJS 3.1.2
Wrong a second time. You can click a keyword and a search is run. So it is linkable.

Sorry for my second comment above (“wrong a second time”). I do understand now the requirement.

But wouldn’t this be a small change in templates/frontend/objects/article_details.tpl , line 138 ?

For example one could use on line templates/frontend/objects/article_details.tpl, line 138:

<a href={url page=“search” query="$keywordItem"}>{$keywordItem|escape}{if !$smarty.foreach.keywords.last}, {/if}

1 Like

Hi @mpbraendle, it’s worked. Nice.

Again, I might be wrong, but @NateWr writes:

The search doesn’t actually match against keywords. If the keyword isn’t also used in the title or abstract, no results will be found.
(Keyword linking · Issue #3853 · pkp/pkp-lib · GitHub)

So it would not be quite correct to link keywords by using search queries. So correct linking will only work when this issue is closed:

Hi everyone,

I just wanted to chime in on this part from the original message:

That issue is filed against 3.2, but primarily in order to adapt our browseBySection plugin into the core application. I don’t think we will include browsing by keyword (or linking) in 3.2.

That’s not because we don’t want to. We really want to make that happen! And when we include it, it should definitely be possible to link the keywords. But unfortunately other higher priorities have crowded it out so far.

1 Like

Dear @NateWr, thanks for the heads-up. That’s a bit unfortunate. Any idea when this could be implemented?


I’m afraid I don’t have a good answer for you. To my knowledge, it is not scheduled formally or informally in any future version. It is a popular request, though.

I’ll tag @israel.cefrin here, who is helping us prioritize UX work for the frontend, so that he is aware. I’ve also asked for some clarity about which part of the issue is scheduled for 3.2, and I will try to split out the different parts of that issue so that we can be more clear about which parts are scheduled or not.


Hi @fpannach,

Just wanted to let you know that I’ve split up the original issue, which combined several different features, so now you can track progress on browsing by keyword here:

I’ve given it the Community Priority tag for now and I believe you may have been in touch with Publishing Services to discuss this further.

Dear @NateWr,
yes we would be willing to sponsor the development if that could help speeding up the implementation.
And thanks for opening up the issues, that does described perfectly what’s needed (at least from our side) and should prevent any misunderstandings in the future.