Cacheid and workcacheid when assigning a category to a new object

I'm trying to figure how Livelink assign categories and attributes to new added objects. I'm looking to further understand this functionnality. I did not find anything on the KC.

At the moment, here's what I figured out. When the user select a category for a new object, Livelink create a workcacheid which is linked with the "plain" category definition. When the user click Apply or Done, or choose another category in the Edit Category dialog this workcacheid is passed with the different fields info and values, (ex:category id and version in the attrset field). A cacheid is then used and the workcacheid is not used anymore.
Each field attribute then have a distinct name like _1_1_11_1_12_1. These fields names can be understood like this:
1_1_ seems to indicate an attribute field
11_1_ designate the attribute subset when there is one, first value
12_1 designate the proper attribute field, first value

When the object is added to Livelink, the cacheId is specified and the categories definition is then "linked" to the object.

Is there anything additionnal which would be helpfull ? Thank you.

Find more posts tagged with

Comments

Hans Stoop

Hi Jean-Philippe,

What are you trying to establish? There may be easier ways of doing this?

Hans

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Mittwoch, 27. März 2013 16:48
To: eLink Recipient
Subject: Cacheid and workcacheid when assigning a category to a new object

Cacheid and workcacheid when assigning a category to a new object

Posted bymartin.jean-philippe@hydro.qc.ca (Martin, Jean-Philippe) On 03-27-2013 11:45

I'm trying to figure how Livelink assign categories and attributes to new added objects. I'm looking to further understand this functionnality. I did not find anything on the KC.

At the moment, here's what I figured out. When the user select a category for a new object, Livelink create a workcacheid which is linked with the "plain" category definition. When the user click Apply or Done, or choose another category in the Edit Category dialog this workcacheid is passed with the different fields info and values, (ex:category id and version in the attrset field). A cacheid is then used and the workcacheid is not used anymore.
Each field attribute then have a distinct name like _1_1_11_1_12_1. These fields names can be understood like this:
1_1_ seems to indicate an attribute field
11_1_ designate the attribute subset when there is one, first value
12_1 designate the proper attribute field, first value!

When the object is added to Livelink, the cacheId is specified and the categories definition is then "linked" to the object.

Is there anything additionnal which would be helpfull ? Thank you.

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Content Server:	Knowledge Center

Jean-Philippe_Martin

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

It's a personnalised "add document" interface. It give the user the hability to see only selected attributes instead of having to select and add each category and seeing the whole list of attributes. In the background though it makes the same url calls as if each actions was done in the web interface.

De : eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Envoyé : mercredi 27 mars 2013 15:05
À : eLink Recipient
Objet : RE Cacheid and workcacheid when assigning a category to a new object

RE Cacheid and workcacheid when assigning a category to a new object Posted by hstoop@opentext.com (Stoop, Hans) On 03-27-2013 15:04

Hi Jean-Philippe, What are you trying to establish? There may be easier ways of doing this? Hans From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Mittwoch, 27. März 2013 16:48
To: eLink Recipient
Subject: Cacheid and workcacheid when assigning a category to a new object Cacheid and workcacheid when assigning a category to a new object

Posted by martin.jean-philippe@hydro.qc.ca (Martin, Jean-Philippe) On 03-27-2013 11:45

I'm trying to figure how Livelink assign categories and attributes to new added objects. I'm looking to further understand this functionnality. I did not find anything on the KC.

At the moment, here's what I figured out. When the user select a category for a new object, Livelink create a workcacheid which is linked with the "plain" category definition. When the user click Apply or Done, or choose another category in the Edit Category dialog this workcacheid is passed with the different fields info and values, (ex:category id and version in the attrset field). A cacheid is then used and the workcacheid is not used anymore.
Each field attribute then have a distinct name like _1_1_11_1_12_1. These fields names can be understood like this:
1_1_ seems to indicate an attribute field
11_1_ designate the attribute subset when there is one, first value
12_1 designate the proper attribute field, first value!

When the object is added to Livelink, the cacheId is specified and the categories definition is then "linked" to the object.

Is there anything additionnal which would be helpfull ? Thank you.

[To post a comment, use the normal reply function]

Forum:

Content Server Development Forum

Content Server:

Knowledge Center

[To post a comment, use the normal reply function]
Topic: Cacheid and workcacheid when assigning a category to a new object
Forum: Content Server Development Forum
Content Server: Knowledge Center

Hans Stoop

The categories need to be collected. This is done in a certain structure. With the function DBGet you get the categories and attributes of an existing node. Have a look in the builder how this is structured. You will see the category definition and separate the attribute values in a similar nested assoc structure.

When you create a new document the same structure has to be created. This structure is not passed along with the request but stored in the database in the cache table. The cacheID is just the value to identify the entry in the cache table. If you save a category what happens is:

<![if !supportLists]>- <![endif]>Get the values from the cache

<![if !supportLists]>- <![endif]>Add(update the edited values

<![if !supportLists]>- <![endif]>Store the new assoc in the cache.

The names you give are the names as used on the HTML page.

As you have discovered this is build of tuples of 2 numbers.

The first number in th etupye is the attribute ID and the second the the sequence number for the value. For single values attributes this sequence number can only be one. For multi-valued attributes this can also have higher numbers.

All but th elast tzple define attribute sets or attribute container.

The first tuple is the category itself. It has always attribute id 1 and can have only 1 value.

If the second tuple it is not the last tuple it is an attribute set attribute (or maybe another set attribute type). It I spossible to have multi-values et attributes. Therefore the sequence number can be higher than 1.

The last tuple is a primitive attribute that has an value of its own.

Currently th emaximal number of tuples is 3.

Hans

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Mittwoch, 27. März 2013 20:23
To: eLink Recipient
Subject: RE RE Cacheid and workcacheid when assigning a category to a new object

RE RE Cacheid and workcacheid when assigning a category to a new object

Posted bymartin.jean-philippe@hydro.qc.ca (Martin, Jean-Philippe) On 03-27-2013 15:22

De : eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Envoyé : mercredi 27 mars 2013 15:05
À : eLink Recipient
Objet : RE Cacheid and workcacheid when assigning a category to a new object
RE Cacheid and workcacheid when assigning a category to a new object

Posted byhstoop@opentext.com (Stoop, Hans) On 03-27-2013 15:04

Hi Jean-Philippe,
What are you trying to establish? There may be easier ways of doing this?
Hans
From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Mittwoch, 27. März 2013 16:48
To: eLink Recipient
Subject: Cacheid and workcacheid when assigning a category to a new object
Cacheid and workcacheid when assigning a category to a new object

Posted by martin.jean-philippe@hydro.qc.ca (Martin, Jean-Philippe) On 03-27-2013 11:45

I'm trying to figure how Livelink assign categories and attributes to new added objects. I'm looking to further understand this functionnality. I did not find anything on the KC.

At the moment, here's what I figured out. When the user select a category for a new object, Livelink create a workcacheid which is linked with the "plain" category definition. When the user click Apply or Done, or choose another category in the Edit Category dialog this workcacheid is passed with the different fields info and values, (ex:category id and version in the attrset field). A cacheid is then used and the workcacheid is not used anymore.
Each field attribute then have a distinct name like _1_1_11_1_12_1. These fields names can be understood like this:
1_1_ seems to indicate an attribute field
11_1_ designate the attribute subset when there is one, first value
12_1 designate the proper attribute field, first value!

When the object is added to Livelink, the cacheId is specified and the categories definition is then "linked" to the object.

Is there anything additionnal which would be helpfull ? Thank you.

[To post a comment, use the normal reply function]
Forum:
Content Server Development Forum
Content Server:
Knowledge Center
[To post a comment, use the normal reply function]
Topic:
Cacheid and workcacheid when assigning a category to a new object
Forum:
Content Server Development Forum
Content Server:
Knowledge Center

[To post a comment, use the normal reply function]
Topic:	Cacheid and workcacheid when assigning a category to a new object
Forum:	Content Server Development Forum
Content Server:	Knowledge Center

Jean-Philippe_Martin

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><![if !supportLists]><![endif]><![if !supportLists]><![endif]><![if !supportLists]><![endif]>

Thank you. It was helpful.

pastedImage_0.png