Closed acouch closed 7 years ago
I'm currently working on my own content types to work with dkan_dataset, replacing the default dkan content types. So I would like to use dkan_dataset, but not dkan_dataset_content_types.
@eindgebruiker Curious to know why you're replacing the default content types?
I need dataset management and dataset storage, just like dkan_dataset/datastore. So I'm very happy to use DKAN. But I don't need all the dataset fields, and need a few of my own. Besides only one resource per dataset is allowed, and a derived resource will be generated by a custom module. A lot to overwrite, so I'd rather create my own content types. This is all to replace the current hybrid Drupal/perl-based www.clio-infra.eu with a full Drupal implementation.
@eindgebruiker Thanks for the feedback. Seems like it would be best to allow the DKAN Datastore to not require DKAN Dataset?
Currently I'm using both DKAN Datastore and DKAN Dataset. It would be easier (for my business case at least) to just replace DKAN Content Types instead of creating my own version of DKAN Dataset.
Now that Additional Info has moved to the main Add dataset form (thanks!) I can achieve most of what I want with form_alters on dkan_dataset, so no more objections from me here. I welcome anything that will make DKAN more flexible, though.
Closing. The main issue here has been completed for some time: https://github.com/NuCivic/dkan/blob/7.x-1.13.4/modules/dkan/dkan_dataset/modules/dkan_dataset_content_types/dkan_dataset_content_types.info#L9
Currently "drush en dkan_dataset" misses the dataset and resource content types because dkan_dataset_content_types is not listed in dkan_dataset.info