Separate admin and public search

[Daniel-KM]

Hi,

It would be great to have an additional feature that separates rules for admin and public searches.

Sincerely,

Daniel Berthereau
Infodoc & Knowledge management

[zerocrates]

To some degree, that's part of the intent of the role overrides, to let you exempt logged-in users (if you chose all the roles, at least) from the hiding. Doing stuff on roles rather than admin/public status is broadly consistent with the way Omeka mostly acts elsewhere (for example, public status on Items applies based on the current user's role, not whether the admin or public side is being viewed).

I'll admit, though, what's there as-is only gets you to a situation where you can decide to hide nothing from people who are logged in, not a different set of hidden elements. What's the use case here? I'd like to avoid doubling up on what's already a very lengthy 2-dimensional form.

[Daniel-KM]

Hi,

The use case is that some librarians use public view to search and when they don't find the result they want, they use the admin view, because they see more fields and because they thinks it's a better engine. Ideally, each field of each set may be hidden or not by each role, for each type of page (there is the browse page too), (three dimensional array). This is not too important, that's why I didn't patch. Pehraps a single checkbox to check or not the theme is enough.

Sincerely,

Daniel Berthereau
Infodoc & Knowledge management