Determine whether it is possible, out of the box, or with some minor modifications to configure the requirement of uploads to be flagged on a per-work-type basis.
Currently, Hyrax has a config.work_requires_files boolean that affects all types in config/initializers/hyrax.rb — but this may be too coarse grained for systems storing multiple (possibly related, possibly not) work types that may or may not require an upload.
Use cases
An aggregate work that is not a collection, e.g. a Newspaper Publication has descriptive metadata, but may have child issues associated. It may make sense for this to be modeled as a work, not a collection, and as such, its children may require file uploads, but it should not.
A system may store something like a catalog entry for a physical item such as a book or curated object that has no digital representation, and a library may want to store this in the same repository as digital works, such as images.
Determine whether it is possible, out of the box, or with some minor modifications to configure the requirement of uploads to be flagged on a per-work-type basis.
Currently, Hyrax has a
config.work_requires_filesboolean that affects all types inconfig/initializers/hyrax.rb— but this may be too coarse grained for systems storing multiple (possibly related, possibly not) work types that may or may not require an upload.Use cases