-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation: How To Create a New Islandora Content Type #85
Comments
Hi @manez , I am a mobile developer and a starter on open source projects. I want to contribute to open source starting with small things as I learn.This is the second issue I found on your repo.Could you please suggest how I can get started on this issue? |
Hi I have a question here! what's the preferred way to create the new content type? do we clone the existing content type structure (i.e. basic image) - rename it? or when I look at the drupal directory, I see content types - collection / basic image are separate module. Do we clone one of the module and make a new module for the new content type (e.g. newspaper, large image ... ) |
pings @daniel-dgi |
good question. i'd seperate out each content type into its own module. then we can have specifics for dealing with that content type (like display) located alongside with it in the same module. |
just thinking about today's call and about @DiegoPino's mention of entities. Would it make sense to create a base entity / content type using Entityform that all islandora objects/content types subscribe to? Eg. an Islandora Archival Entity (fedora: mixinTypes = islandora:archival)? It just stores a compliant pcdm fedora object (binary/metadata). The other content types, like Basic Image, extend the Archival Entity using Entityform and Entity Reference and include camel workflows and further pcdm'ing. Not sure if that helps or confuses things. |
@dmoses, this is in tune with my idea. I'm still in an exploratory stage to evaluate with real code what works best/ level of granularity, but having a base one that describes a base pcdm:Object is my idea, then extend (by aggregating the needed/extra triples, workflows, etc. But i'm also proposing (also exploration) it could be good to also have binary/fedora3 dat stream concept as a separate one linked to the main one. |
Only Basic Image and Collection are really viable right now, but even these might be cases where users will want to clone & customize from the default versions. A How-To going through this with screenshots would be a good addition to our documentation.
The text was updated successfully, but these errors were encountered: