In this issue, we administer the different contexts in which a list of publications is to be shown.
This will help in making researchr cleaner and more robust by moving away from the PublicationList entities, which were originally introduced to have (the non-search version of) faceting in researchr.

By having a generic interface for displaying publications in a context, it will reduce the complexity by removing various types of PublicationList entities and templates for displaying them.

Context item	Non-standard facets	Non-standard sorting	Context-specific publication view	Most appropriate searcher
Bibliography	Ranking, Classification scheme		Yes (remove from bib control)	PublicationSearcher/PubInBibSearcher
Bibliography: Recently Added	no facets at all is OK	Date added	Yes (show add date, remove from bib control)	PubInBibSearcher
Bibliography: Recently Removed	no facets at all is OK	Date removed	Yes (show remove date)	PubInBibSearcher
Person			No (?)	PublicationSearcher
Alias			No (?)	PublicationSearcher
Profile			Yes (remove when not authored by me?)	PublicationSearcher
Tag			No	PublicationSearcher
ConferenceSeries			No	PublicationSearcher
Publication search		Relevance wrt query	No	PublicationSearcher

Some problems to think about:

• We probably need to keep PubInBib entity to account for the date added/removed from bibliography. Reason: We don’t want dates of additions/removals to any bibliography to be indexed in the scope of a publication. That would lead to retrieval of all addition/removal dates in case of change in any searchable data for Publication, because documents in the search index are completely recreated when there is a change in one of its search fields.
• PubInBib is also needed to enable faceting on classification/ranking schemes
• To display the publications when using a PubInBibSearcher, we need to translate a PubInBib result to Publication (by mapping it to pib.publication)
• Searchable data of PubInBib is not similar to Publication, so when using a PubInBibSearcher, we cannot get facets like year, venue and author from it.

Submitted by Elmer van Chastelet on 15 December 2012 at 13:35

Depends on: Add support for dynamic search fields

To get rid of PubInBib, we want to use dynamic search fields. Unfortunately, implementation is not completed. Not sure if this feature is going to work at all with faceting (see comments in above mentioned issue)

-

I think we should keep using PubInBib for the cases described in this issue. In general, additional Publication metadata specific to a bibliography can be isolated using the PubInBib entity. This won’t hinder us from removing the PublicationList entities and all maintenance (init/update/reset) related code.