Enable person entity functionality at the view level
The new feature (May 2024) for person entities is either on or off for all views.
For some special-purpose views it may be inappropriate to display person entity cards. At present the library would have to deploy a customisation package to allow it to show on some views, but hide it on others. It would be simpler to enable via check boxes in a view's general tab.
Libraries should be able to configure whether or not the results returned in the carousels on a person entity page are controlled by the view's search scopes. e.g. titles that are excluded from that view should display or not.
Peta Hopkins
shared this idea
-
The December 2024 release notes, under additional enhancements, it advises:
Support Configuration of Person Entity at the View Level – Previously, the suggestions of persons in autocomplete and Person Info Card features were enabled only at the institution level. With this enhancement, you can now enable/disable these features at the view level with the following new fields on the General tab of the View Configuration page (Configuration > Discovery > Display Configuration > View Configuration)This probably should be set to complete.
Although it doesn't make any mention of being able to control the scope of the links ie. should the links displayed be limited to the scope of that particular view. Might need some more testing to see if that is also addressed. -
Lihong Zhu commented
According to Ex Libris documentation "Searching Linked Open Data - Person Entity" (https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/150End_User_Help/Searching_Linked_Open_Data_-_Person_Entity), in the section "Configuration Options", it has the following:
View Configuration page (Configuration > Discovery > Display Configuration > Configure Views):
The following parameters enable person entity per view:Enable Person Entity Autocomplete – This option enables autocomplete for person entities. This option is disabled by default.
Enable Person Entity Info Card – This option enables the display of the Person Info Card on the Full Display page. This option is disabled by default.
Is the above configuration option doing the same thing as suggested it in this Idea Exchange? If yes, should we close this Idea Exchange so that people can free their votes for something else? Thanks.
-
Manu_Schwendener
commented
+1
-
Leslie Starasta
commented
Functionality at the view level would allow adequate testing of the feature before implementation.
-
Elliot Williams
commented
This would also allow sites with standard sandboxes to test the feature more effectively. Since the standard sandbox doesn't have our local data, we can't see how the person entities would look for our actual records. Being able to enable it on specific views would allow us to see how it works with our real data, which would make it easier to make the case to colleagues for why this is a valuable feature.
-
Simon Read
commented
I support the addition of view specific configuration. It is particularly important that titles that appear on the person entity card are actually accessible via that view. At the moment we can see electronic titles on the person entity card that users can't access because those titles aren't activated for that view (in our case we're using available for groups to control view level access). We can't realistically use the person entity functionality until this has been resolved
-
Cindy Bowen
commented
I'm also out of votes, but strongly support being able to enable this functionality at the view level and adjust what titles are displayed for each view.
-
Beth Juhl
commented
I'm out of votes but we have certain views where the entity cards would not be appropriate.