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

Customize item lists #859

Closed
manthey opened this issue May 19, 2022 · 2 comments
Closed

Customize item lists #859

manthey opened this issue May 19, 2022 · 2 comments

Comments

@manthey
Copy link
Member

manthey commented May 19, 2022

Currently, item lists can contain thumbnails, macro, and label images based on whether the current user is unset, a regular user, or an admin. Similarly, images and metadata can be shown in an item page based on this. Eventually, we want to display columns of metadata in the hierarchy lists, too.

It would be nicer if this could be configured on a per-folder, per-collection, or per-user level.

@manthey
Copy link
Member Author

manthey commented May 19, 2022

This could be done by fetching a folder-specific config file (that, if no such file is found, would walk up the folder parents until such a file is found).

The file would be named something appropriate like .large_image_config.yaml and could contain a variety of settings: e.g.,

-
item_page:
  images:
    - macro
access:
  user:
    item_page:
      images:
        - label
        - macro
    item_list:
      images:
        - label
        - macro
      columns:
        - meta.ranking
  admin:
    item_page:
      images:
        - label
        - macro
        - "*"
      metadata:
        - tile
        - internal

We probably want a global file specified in settings in case no other config file is found.

Also, should nested config files be merged (or optionally merged)? It seems like that would be more confusing than useful (and you'd need a debug method to determine why the resultant config is what occurred).

I image that before the hierarchy widget or item page is rendered, we would fetch the config file and then change what gets rendered based on that.

@manthey
Copy link
Member Author

manthey commented Aug 12, 2022

Added in #901.

@manthey manthey closed this as completed Aug 12, 2022
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

1 participant