...
Time | Item | Who | Notes |
---|---|---|---|
Batch Upload Work |
| ||
Metadata and Media Worktype | Becasue of AV type that Avalon cares about - Indiana and NU worked on AV worktype for Hyrax. Get worktype tied to player. IIIF Manifest generation. Metadata connected. Dealing with multipart fields. Store all of the multivalued/ multipart fields as a JSON blob in one statement. Other thing with the worktype - our descriptive metadata isn't tied to media. Does a betteer job than generic metadata. Reviewing generic worktype - push some of our opinion of metadata into Hyrax core via Generic worktype. Happening in Metadata IG sponsoring a session for those interested - hash out what's there, what should be there. Descriptive for generic work. Offering use cases. Some of what we like in media we're seeing fi we can push to Generic. | ||
"Owner" question from LaRita | Part of the Permission and Analysis WG - PAWG. Question of whether "owner" role currently in Hyrax - what is an owner? What's special about that role? Permissions - list of actiosn assigned to roles - make sure list of actions is complete per role. Discussion was all about - are we covering what people think of when they think of an owner. Different perspectives from people with different backgrounds. Conclusion: We do cover everything in the Matrix of actions. Everything can be configured if we do a configurable permissions module. Whomever creates a work is an Owner - an immutable role. PAWG is leaning toward a work should have a primary contact. A descriptive field for Primary contact. Who is the creator. Those are just descriptive fields. | ||
IIIF Presentation 3.0 support in Hyrax (and allowing configurable viewers) | |||
First meeting of the Hyrax working group | |||
PR and Hyrax |
...