Skip to content

Work Type Inheritence

Randall Floyd edited this page Jun 22, 2018 · 1 revision

Use cases might dictate specialties of work types and imply the ability to share behaviors of closely related things. Currently you can generate a new work type in Hyrax, but ideally you should also be able to say it is 'a kind of' work type, thus allowing a hierarchy of inheritance. This is a page to collect some design thoughts on how that might work.

To get a feel for what a derived work type might look like, here's a hard coded example of one work type inheriting from and mixing in behaviors of a base 'archetype':

https://github.com/IUBLibTech/catorax/commit/8768fd1e7d6139e73018b324104a503011c8b70e

Clone this wiki locally