I'd recommend looking at entity relationships (especially those with foreign
keys). For example, by including any of the *Role entities you would be
including the Party, RoleType and other such entities in the party component.
The same may be true of other components. In other words, you're implicitly
talking about including those things as well.
Also, why not include the Survey* entities? Do those depend on something you
want to leave out, or are you just not interested in the idea of dynamic forms?
-David
On Feb 24, 2010, at 10:52 PM, Christopher Snow wrote:
> I have documented my thoughts in OFBIZ-3505
>
> Feedback please everyone!
>
>
> Christopher Snow wrote:
>> Hi Devs, do any of you have an opinion on what entities would stay in
>> content if it was migrated to framework, and what entities would move to
>> contentext? My ideas are below...
>>
>> Many thanks,
>>
>> Chris
>>
>>
>> Christopher Snow wrote:
>>> Hi Jacopo,
>>>
>>> I will try and identify exactly which entities would be required in
>>> content, and those required in contentext. In the meantime, would you agree
>>> with the following list?
>>>
>>> Component CONTENT
>>>
>>> view AssocRevisionItemView
>>> view ContentAssocRevisionItemView
>>> view MaxRevisionItemView
>>> view MaxContentApprovalView
>>> view ContentAssocOptViewFrom
>>> view ContentRevisionItemAndContentApprovalView
>>>
>>> entity Content
>>> view ContentAndRole
>>> entity ContentApproval
>>> entity ContentAssoc
>>> view ContentAssocDataResourceViewFrom
>>> view ContentAssocDataResourceViewTo
>>> entity ContentAssocPredicate
>>> view ContentAssocViewFrom
>>> view ContentAssocViewTo
>>> entity ContentAttribute
>>> view ContentDataResourceView
>>> entity ContentMetaData
>>> entity ContentOperation
>>> entity ContentPurpose
>>> entity ContentPurposeOperation
>>> entity ContentPurposeType
>>> entity ContentRevision
>>> entity ContentRevisionItem
>>> entity ContentRole
>>> entity ContentType
>>> entity ContentTypeAttr
>>> view SubContentDataResourceView
>>>
>>> entity AudioDataResource
>>> entity CharacterSet
>>> entity DataCategory
>>> entity DataResource
>>> entity DataResourceAttribute
>>> view DataResourceContentView
>>> entity DataResourceMetaData
>>> entity DataResourcePurpose
>>> entity DataResourceRole
>>> entity DataResourceType
>>> entity DataResourceTypeAttr
>>> entity DataTemplateType
>>> entity ElectronicText
>>> entity FileExtension
>>> entity ImageDataResource
>>> entity MetaDataPredicate
>>> entity MimeType
>>> entity MimeTypeHtmlTemplate
>>> entity OtherDataResource
>>> entity VideoDataResource
>>>
>>> entity Document
>>> entity DocumentAttribute
>>> entity DocumentType
>>> entity DocumentTypeAttr
>>>
>>> entity WebPreferenceType
>>> entity WebUserPreference
>>>
>>> extend-entity WebPage
>>> entity WebSiteContent
>>> view WebSiteAndContent
>>> entity WebSiteContentType
>>> entity WebSitePathAlias
>>> entity WebSitePublishPoint
>>> entity WebSiteRole
>>> view ContentAssocAndContentPurpose
>>>
>>> Component CONTENTEXT
>>>
>>> entity Survey
>>> entity SurveyApplType
>>> entity SurveyMultiResp
>>> entity SurveyMultiRespColumn
>>> entity SurveyPage
>>> entity SurveyQuestion
>>> view SurveyQuestionAndAppl
>>> entity SurveyQuestionAppl
>>> entity SurveyQuestionCategory
>>> entity SurveyQuestionOption
>>> entity SurveyQuestionType
>>> entity SurveyResponse
>>> view SurveyResponseAndAnswer
>>> entity SurveyResponseAnswer
>>> entity SurveyTrigger
>>>
>>> Many thanks,
>>>
>>> Chris
>>>
>>> Jacopo Cappellato wrote:
>>>> Chris,
>>>>
>>>> thanks for your report:
>>>>
>>>> On Feb 24, 2010, at 12:50 PM, Christopher Snow wrote:
>>>>
>>>>
>>>>> With "help" dependent on content, I believe content should be moved into
>>>>> the framework.
>>>>>
>>>>>
>>>>
>>>> IMO the content should be split into two parts: one will go into the
>>>> framework, the other one ("contentext") will stay in the applications
>>>>
>>>>
>>>>> One of the main dependencies in content is from survey to order. One
>>>>> option is to remove survey into it's own dedicated component. Any
>>>>> thoughts on this?
>>>>>
>>>>>
>>>>
>>>> This could be a good candidate for the "contentext" component I have
>>>> mentioned before.
>>>>
>>>>
>>>>> The other main dependency is on party. I believe we should move the core
>>>>> party stuff (Party, PartyAttribute, PartyTypeAttr, PartyGroup, PartyType,
>>>>> PartyRole, RoleType) into a partycore component that is part of the
>>>>> framework. Any thoughts on this?
>>>>>
>>>>>
>>>>
>>>> I still think (and hope) that the framework will be able to live without
>>>> dependencies on Party; we should carefully evaluate the current
>>>> dependencies and see if we can resolve them.
>>>>
>>>>
>>>>> Content also has a dependency on Person via WebSiteRole. I'm not sure
>>>>> Person should become part of partycore. However, I'm not sure that
>>>>> Person should be part of WebSiteRole. Any thoughts on this?
>>>>>
>>>>>
>>>>
>>>> The dependency on Person should be removed from the data model: this
>>>> should be a simple task to perform.
>>>>
>>>> Kind regards,
>>>>
>>>> Jacopo
>>>>
>>>>
>>>
>>
>
