Connecting to database in DCT

Hi all,

We need to set extended attributes to a particular content file (pdf, doc..), and these attributes needs to be stored in our database. can we create DCT which will have UI to capture attribute values from user? can we write logic or call a java class inside DCT to connect with database>

Thanks in advance.

-Regards

Manoj

Find more posts tagged with

Comments

Adam Stoller

Hi all,

We need to set extended attributes to a particular content file (pdf, doc..), and these attributes needs to be stored in our database. can we create DCT which will have UI to capture attribute values from user? can we write logic or call a java class inside DCT to connect with database>

Thanks in advance.

-Regards

Manoj

If you're just trying to set EAs on a non-templated piece of content - have you considered setting up the TagUI for such purposes? (File > Tag)

Once the EAs are attached to the asset you can use DD to deploy them to a DB.

Or are you saying that you already have a DCT and that there is a field within the DCT that references a non-templated asset? In which case you should be able to configure DD to deploy the contents of that field to a DB.

ManojK

Thanks for reply.

we are trying to achieve same you mentioned in second point.

Let me tell you the actual scenario, one thing is sure that we have to set attribute to the contents. We have to take decision whether to write our own custom logic and UI for setting attribute or leverage Teamsite's DCT's or tagging UI whichever is suitable to achieve the same. As per our requirement in both cases we have to maintaing our own database to maintain the attribute values.

-Regards
Manoj

Adam Stoller

Thanks for reply.

we are trying to achieve same you mentioned in second point.

Let me tell you the actual scenario, one thing is sure that we have to set attribute to the contents. We have to take decision whether to write our own custom logic and UI for setting attribute or leverage Teamsite's DCT's or tagging UI whichever is suitable to achieve the same. As per our requirement in both cases we have to maintaing our own database to maintain the attribute values.

-Regards
Manoj

So - you have a field in DCT-A that allows someone to reference a non-templated asset (browse button?) that will populate that field with a path.

As stated - you can configure your DD config file to deploy that field to the DB.

Or you can add some FormAPI code (onSaveValid event probably) that does a callServer request to a script that retrieves that field value and sets an EA on the DCR with that value - and then use DD to deploy that EA to the database.

Or (if you require a tagging step in your workflow) - you could configure FormAPI code in the TagUI to do pretty much what was just described above - extract the data from the DCR and set it as an EA - and then use DD to deploy that EA to the database.

In all such cases - you also have the option to roll-your-own DB transfer script process rather than using DD.

No matter how you slice it - there's going to be some customizations needed - but the first method (DD'ing the field in the DCR) probably involves the least amount of that customization.