#733: WebSearch: more flexible detailed record page tabs for files
-------------------------+----------------------
Reporter: simko | Owner: ppraczyk
Type: enhancement | Status: new
Priority: major | Milestone:
Component: WebSearch | Version:
Keywords: |
-------------------------+----------------------
1) Currently we have two tabs to display attached file objects, Files
and Plots. The dispatching logic is such that everything that is a
non-plot goes into the Files tab and is presented in a new section
there depending on the document type. For example, the Supplementary
Material is a simple sub-section of the Files tab and looks like
[[http://inspirebeta.net/record/870473/files/]].
We should make this setup more configurable. For example, it would be
useful to split the Files tab dynamically into more tabs, say
Fulltext, Supplementary Material, Plots, Data, etc, depending on the
file type. We can achieve this via a new configuration variable like:
{{{
CFG_WEBSEARCH_DETAILED_RECORD_PAGE_FILE_TABS = {
'Fulltext': ('arXiv', 'Main', 'Springer'),
'Supplementary Material': ('Additional',),
'Plots': ('Plot', 'Figure'),
'Files': ('*',)
}
}}}
that people could tweak. The last rule can be implicit and not even
mentioned. That is, if there is no special file tab defined for the
given file object, display it in the Files tab, as is the case now.
This would provide also backwards compatibility.
2) Note also that the detailed record page setup lives in the DB,
because the visibility of concrete tabs can be configured per
collection. See table `collectiondetailedrecordpagetabs`. So this
part should be addressed as part of this ticket too. For example,
instead of a CFG variable as suggested above, one could put all the
configuration setup in the DB, including rules for dynamic Files tab
generation. However, this should not be necessary, we can simply
leave the rest of the tabs machinery as it is now, and treat only the
Files tab in this special, dynamically-expandable way.
3) Note also that it would be useful to sometimes treat files hosted
on external URLs in the same way as files hosted internally. For
example, to point to a fulltext paper that is hosted on arXiv in the
Fulltext tab. This may be split into another ticket though, since it
touches displaying non-local, external files that are stored in 856
only, together with locally-hosted files. But it is good to foresee
this future possibility as part of this ticket.
--
Ticket URL: <http://invenio-software.org/ticket/733>
Invenio <http://invenio-software.org>
