PKP Bugzilla – Bug 8255
Proposals concerning SEO and URL forwarding in OJS
Last modified: 2013-06-13 00:17:35 PDT
We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.
I've proposals concerning SEO and URL forwarding in OJS.
So the major improvement will be adding a Search Engine Friendly URLs as it's done in Joomla CMS.
As for example a new core functionality could translate old article's URLs to a new ones automatically or semi automatically. Function can take article's title stripe unused symbols, convert to lowercase and change space symbols to "-". This URL also could be editable by editor. So no modifications needs to be done to import plugins. Also internal 302 redirect should be done to redirect queries from old URLs to new ones.
Another thing concerning URL comes out of a multilanguage support.
Each journal has it's own path which is editable. But it's editable only for a one common language what is unacceptable for multilanguage OJS instance. So the physical path should remain but "mask/translation" for another locales should be supportable. So when we will change the locale the journal's URL should change to corresponding one.
Another thing is that welcome/home page don't have a keyword, description and intro description (for all hosted journals, which could be done as a text paragraph before journal's list) fields which could be filled in site administrators area.
Thanks for the suggestions, Garant. The first one (search engine friendly article URLs) is possible by enabling identifiers for published content in Journal Setup; when that's done, you'll be able to optionally enter identifiers for articles, supplementary files, and article galleys. These will take over from the numeric IDs that are used by default.
I'm glad that I can offer some enhancements.
Thank you, I've found those optional identifiers but there is a little problem, they are also used for a single locale not multi :)
Yes, we've had to make some tough decisions around how to treat multilingual content.
In OMP (for monographs), different languages of the same book are considered entirely different editions, with totally different identifiers (e.g. ISBNs).
That doesn't seem to be the case for journals -- a translation of the same article is often treated as the same entity.
This isn't just an issue for the front end, it's also an issue for interacting with external systems, e.g. CrossRef, PubMed Central, DOAJ, etc.; so we can't make a decision on multilingual support without affecting all of those too. The current structure is the best match for those.
There are some improvements we can certainly make, like allowing the specification of a locale in the URL. We have to tread carefully so that we don't change existing URLs, though.
Thank you for explanations!