Bug 114312

Summary: No way for generic assets to augment the authoring kit for all content types
Product: [Retired] Red Hat Enterprise CMS Reporter: Daniel Berrangé <berrange>
Component: content typesAssignee: Daniel Berrangé <berrange>
Status: CLOSED WONTFIX QA Contact: Jon Orris <jorris>
Severity: medium Docs Contact:
Priority: medium    
Version: nightly   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-09-02 17:45:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Daniel Berrangé 2004-01-26 15:21:06 UTC 
Description of problem:
Each content type is reponsible for registering an authoring kit for
itself. There are, however, a number of genral purpose assets such as
dublin core, file attachments and related links which need to augment
the authoring kits for all content types in the CMS. Obviously the
master content type kit definitions themselves can't reference these
assets, since the is no way to know in advance if an asset will be
installed on the system.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Daniel Berrangé 2004-01-26 15:29:04 UTC 
I have a solution pending checkin as follows:

Create an abstract class called ContentAssetInitializer. Generic
assets such as dublin core, related links, etc subclass this and
implement the abstract methods to return information about their
drop-in authoring kit step. 

     /**
     * The base type against which the asset is defined,
     * typically com.arsdigita.cms.ContentPage
     */
    public abstract String getBaseType();
    /**
     * The class of the authoring kit step
     */
    public abstract Class getAuthoringStep();

    /**
     * The label for the authoring step
     */
    public abstract GlobalizedMessage getAuthoringStepLabel();
    /**
     * The description for the authoring step
     */
    public abstract GlobalizedMessage getAuthoringStepDescription();

Upon startup the step for these assets are registered with
AuthoringKitWizard UI class such that when it loads an authoring kit
from the DB, it appends the steps for all registered assets.
Comment 2 Daniel Berrangé 2004-01-28 15:10:31 UTC 
This was submitted in p4 39749, 39751
Comment 3 David Lawrence 2006-07-18 03:30:52 UTC 
QA_READY has been deprecated in favor of ON_QA. Please use ON_QA in the future.
Moving to ON_QA.
Comment 4 Daniel Berrangé 2006-09-02 17:45:45 UTC 
Closing old tickets