Jim Safley
Jim Safley
This is the selection sidebar after clicking "Omeka resource" > "Item sets" on the item add/edit page.
Probably add quick-add as well. The behavior should be the same as linking items.
This is now fixed for editors. We'll look into showing the checkboxes only if the current user has edit permissions for the resource _and_ has `batch_update` permission.
The RDF way of defining a resource's class is `rdf:type`. So we could correctly label the class as "Type", but I see how people may conflate that with `dcterms:type`.
Since this discussion we've added resource page blocks, so it is now possible to add a "Resource class" block that renders the resource class and only the resource class on...
This is addressed in #1882. Omeka will now look out to the term if the value's `property_id` is "auto".
We'll look into batch edit as well.
The only way I see this working is changing the Browse navigation link from a MVC page to a URI page, like this: ```php // Omeka\Site\Navigation\Link\Browse::toZend() public function toZend(array $data,...
Possibly use the `default-value` class that's set to Title and Description?
> I'm guessing it's okay because when I change it to a random string it does update and when I change it back I get the same results as shown...