Bug 4038 - Use a more descriptive <title /> on pdfInterstitial.pdf
Use a more descriptive <title /> on pdfInterstitial.pdf
Status: RESOLVED WONTFIX
Product: OJS
Classification: Unclassified
Component: General
To be determined
All All
: P5 trivial
Assigned To: PKP Support
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-02 20:29 PST by Felipe Lav
Modified: 2013-05-29 15:22 PDT (History)
1 user (show)

See Also:
Version Reported In:
Also Affects:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felipe Lav 2009-02-02 20:29:32 PST
Currently, the <title> tag for all pages displayed with the pdfInterstitial.pdf template is set to the same string: {translate key="article.pdf.title"}, which is something like "Portable Document Format (PDF)"

Even though it seems that these pages are not indexed by Google (and probably other search engines, because of the refresh that redirects to the actual PDF), "Content by Title" reports (such as in Google Analytics) are less useful since there'll be a disproportionate amount of hits on "Portable Document Format (PDF)". Even though it's possible to decompose this info and eventually find out which articles are most read, I think it would be better to add information about the article that will be displayed in the title; not only because of producing easier-to-understand stats (and the possibility to look for most read authors), but also because the title should be descriptive of the content that's about to be shown.

According to the HTML 4.01 Spec:

> Authors should use the TITLE element to identify the contents of a document. Since users often consult documents out of context, authors should provide context-rich titles. Thus, instead of a title such as "Introduction", which doesn't provide much contextual background, authors should supply a title such as "Introduction to Medieval Bee-Keeping" instead.

> For reasons of accessibility, user agents must always make the content of the TITLE element available to users (including TITLE elements that occur in frames). The mechanism for doing so depends on the user agent (e.g., as a caption, spoken).

And, in the Web Content Accessibility Guidelines:

12. Provide context and orientation information

and

14. Ensure that documents are clear and simple


Plus, there's the semantic gain.

I propose that it should probably be set to something like this:

<title>{$article->getArticleTitle()|escape} | {$article->getFirstAuthor(true)|escape} | {translate key="article.pdf.title"} | {$currentJournal->getJournalTitle()|escape}</title>
Comment 1 Alec Smecher 2013-05-29 15:22:51 PDT
This page has been removed in favour of the pdfobject toolset.