Visually "compact" certain fields in item templates?

[peter_b]

Hi everyone

I was wondering if there is a way to visually “compact” (mostly optional) fields for an item?

For example:

If I have 20 fields for an item, and 8 fields are “the most important/popular” ones being used/populated, could I configure the others to somehow “fold” by default, and be opened/used on demand during edit/input?
(to use up less visual space and feel less overwhelming for a cataloger to work with)

Thank you very much in advance!

[cnorton]

To my knowledge, there’s no way to do this by default, however if you or a teammember are comfortable with PHP, the show.phtml file can be modified for the theme you’re using to accomplish this.

[peter_b]

@cnorton: Thanks for the suggestion!

I was already thinking to patch-the-code as an option, but thought it’d be better to ask here before doing that.

Hm… since there are templates, it might actually be possible to cleanly maintain it ourselves - and share easily.

I assume you meant this “show.phtml”?
application/view/omeka/admin/resource-template/show.phtml

I’d need to add an additional property, like $resourceTemplateProperty->foldByDefault(), right?

[bureaujorwert]

My (late) 2 cents
The last couple of years I created simple interfaces for data input, using Vuejs and the RESTful API.
With frameworks like Quasar you have access to tables, input forms, without a lot of coding.
That way you’re unlikely to get in trouble when an update of Omeka occurs.

Cheers,
Hans Ruedisueli

[peter_b]

@bureaujorwert : hm. interesting!

Would you have some code/examples to share regarding your work on Omeka-data setups? Thanks!

[bureaujorwert]

Hi Peter,
Using the RESTful API you’re not restricted to Vuejs, the documentation is your friend: REST API - Omeka S Developer Documentation
If you use Vuejs (I use it often with a nodejs API as a mapper) you’ll be using the axios lib a lot.
For PHP aficionados you could think of Laravel as a frontend for the Omeka API.
I’m sure I can whip up examples some day, but for the moment I don’t have the time to give you one.
Just shut down my Omeka S demo server used for demonstrating the use of the API.
Maybe I’ll find the time to build another, but not soon, sorry.

If you have further questions, I’ll be glad to help, but I have some time restrictions.
Cheers,
Hans Ruedisueli

[peter_b]

Using REST API, VueJS, etc sounds more like coding a completely different UI on its own… Or am I understanding you incorrectly?

I won’t be able to go down this road (neither template nor API code) at the moment, but maybe later in our project’s roadmap.

Thanks for all your suggestions though!

[bureaujorwert]

Indeed Peter,
This way I can create an UI that’s specifically made for a project, volunteers, etc. , giving you much more control over access, and input restrictions.
Volunteers are not confronted with a ‘daunting’ Omeka interface and don’t need much training.
Vuejs is also very useful for creating interactive presentations like touchscreens and mobile applications.
Cheers,
Hans Ruedisueli