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.
-
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.