Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display Label for browse pages #4

Open
alexdryden opened this issue Jun 3, 2024 · 6 comments
Open

Display Label for browse pages #4

alexdryden opened this issue Jun 3, 2024 · 6 comments

Comments

@alexdryden
Copy link

alexdryden commented Jun 3, 2024

Users report that the terms "Item" and "Item set" can be confusing public facing terms in the context of their collections.

This might be a big lift from a development perspective, it might be worth seeing if there is a way to meet the need with existing options.

@alexdryden
Copy link
Author

Workaround:

Instead of making Browse pages from the navigation interface, make a standard page with Browse Preview from the Pages interface:
Screenshot 2024-06-03 at 1 52 10 PM

Public facing:
Screenshot 2024-06-03 at 1 55 31 PM

Use the preferred terminology for the page's url and the page title, and (optionally) the title for the Browse Preview block. Set the number of results to show to a large number so that all relevant results are displayed and set the Link Text to empty so that no "See all" link is displayed.

Evaluation:

This allows the correct terminology to be used in the title and the url slug, and it isn't significantly more work than creating a browse page. The major downside to this approach is that results will not be paginated, which may make this a poor fit if there are a lot of results. Also, leaving the "See all" link black is super hacky and could lead to confusing states (e.g., not all matching results are displayed in the "preview" but there is no indication that the result set is incomplete.)

Overall, I'd say this is a great fix and if this issue is a priority then a better solution needs to be developed.

@graykr
Copy link

graykr commented Jun 3, 2024

@alexdryden That is an interesting hack with the high browse limit and blank "view more" text! It does seem to work.

@alexdryden
Copy link
Author

@graykr if you think this will work for you, great! I'll keep this issue open in case we do find that the lack of pagination will be an issue.

@graykr
Copy link

graykr commented Jun 5, 2024

@alexdryden I'd still like to see the original issue fixed, but it does seem like other issues would be more of a priority! We do still see the "items" label if we browse from the "metadata browse" link:

For example;
https://scp.library.illinois.edu/omeka-s/s/test-ihlc-oral-histories/item?Search=&property%5B0%5D%5Bproperty%5D=6&property%5B0%5D%5Btype%5D=eq&property%5B0%5D%5Btext%5D=Dana%20Miller

The other place it comes up (and perhaps should be a separate ticket) is with browsing item sets:
https://scp.library.illinois.edu/omeka-s/s/test-ihlc-oral-histories/item-set/9782

@alexdryden
Copy link
Author

Yeah, those two end points, /item and /item-set, are going to be involved in a lot of pages and features, potentially. Making the change globally would be a too big of an undertaking for us to consider without upstream support. Because I don't think the developers would see the terminology as a bug, I'll start this discussion in the forum rather than their github repo, where I'm betting it wouldn't get much traction. I may not get to it this week, but if I get the discussion started, would you mind chiming in with some of the disciplinary reasoning for being able to control language used for those headings? That might encourage other non-technical users to chime in as well if they have similar needs.

@graykr
Copy link

graykr commented Jun 5, 2024

@alexdryden That makes sense. It would be wonderful if Omeka could do something with the "class" variable as an option to modify the label (so instead of "items" it could say "interviews" since the items are of class interview). I'm happy to add information as needed -- is the forum another login for me to create, or would this be adding detail to something you draft outside of the forum first?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants