Thursday 03 November 2011 9:12:43 pm - 3 replies
A friend and i are developping a site where we have to register some "research projects" from our University. A project is an article in EZ and author/researcher should be a select field in the article listing all possible authors, where users would choose the one whose is responsible for that project. In the frontend template i'll need to know which researcher is related with which project. For example, a link to list all projects from an especific researcher. Moreover, researchers should be sorted by alphabetical order and users should be able to add, edit and delete researchers.
I have no ideia how to do this.. may anyone help us with some suggestions?
(brazilian here.. sorry about my english
Thursday 03 November 2011 9:24:38 pm
Welcome to the eZ Community!
I think you'll have to change your game plan (at least a little bit) since no datatype that I know of supports all the features your wishing you could pack into a single datatype / content object attribute.
You could use the selection datatype, but that is fairly limited (in terms of your requirements), http://doc.ez.no/eZ-Publish/Technical-manual/4.x/Reference/Datatypes/Selection
You could also use the Authors datatype, but it is much like the selection datatype fairly limited (in terms of your requirements), http://doc.ez.no/eZ-Publish/Technical-manual/4.x/Reference/Datatypes/Authors
You could use the the object relations datatype (This is what I would use for your use case), http://doc.ez.no/eZ-Publish/Technical-manual/4.x/Reference/Datatypes/Object-relations
You could create a custom datatype but it sounds like your a little new to eZ Publish to be able to successfully jump into datatype development on your own without first hand training and experiance.
I would use the object relations datatype because it allows for as many relations as you require to be stored within a content object attribute.
With the object relations datatype I would add user content objects as relations within the attribute. Within a custom template override you would be able to output the users in whatever order or format you desire (using template code).
For administration you can place all the users who are used in object relations content into a single user group to make it simple to administer the available users for selection within object relations content.
I hope this helps ...
Modified on Thursday 03 November 2011 9:27:39 pm by Heath Heath
Thursday 03 November 2011 11:34:24 pm
Your very welcome. Happy to help.
You could let us all know how your solution works out, or if you have further questions related to this thread simply post an update here.
Feel free to create another thread here in the forums if you have any other further questions, we are here to help
You must be logged in to post messages in this topic!