Open maethu opened 11 years ago
I see two options:
Subject
field for this, which is already indexed and quite easy to use. Adding the subjects we use in init-content would make them already selectable and we could then build the views so that they just query the necessary subject. It is also possible to isolate the selectable subject per content type.typing
package (e.g. ftw.typing
) which provides a schema extender with a field for selecting the types. Selecting a "type" makes the content provide the associated marker interface which can then be used for querying in the views.
For the types vocabulary we could use collective.vdexvocabulary.
For adding a new type one would have to implement a marker interface and register it in the vdex vocabualary so that it is selectable.
We could also provide two schema extenders, a single-valued one and a multi-valued one which can be activated with a separate marker interface on the types we want to have it.I think if the subject option (1) does work it would be much simpler to implement. @freinhard @treinhard @phabegger @maethu @ninfaj what do you think? How should we proceed?
I prefer option 1. We do not need more at time. Limit the selectable subject is a must. Something like that:
Try not to touch ftw.contentpage (IOrgunitMarker).
Mark Content with subscriber after edit (Radiobuttons)