The 'inverse' to #153. While object selection should list the entities the object refers to, entity selection should show how many objects link to the entity. This now works for places, but not for people or time periods. The process is completely the same though, we only need to streamline and refactor things a bit.
Also requires some work on the query side. There should be no top_places argument any more (but a top_references?), and proper division of people/places/periods in the JSON response.
(BTW: this also relates to the issue of local vs. filtered search, #127. When coming via the item, selecting a referenced entity moves to filtered search. When coming via the entity, selecting the inbound references moves to a local search.)
The 'inverse' to #153. While object selection should list the entities the object refers to, entity selection should show how many objects link to the entity. This now works for places, but not for people or time periods. The process is completely the same though, we only need to streamline and refactor things a bit.
Also requires some work on the query side. There should be no
top_places
argument any more (but atop_references
?), and proper division of people/places/periods in the JSON response.(BTW: this also relates to the issue of local vs. filtered search, #127. When coming via the item, selecting a referenced entity moves to filtered search. When coming via the entity, selecting the inbound references moves to a local search.)