nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Metadata retrieval API

gzevin

This question belongs to many forums I believe, but I decide to post to the generic one.

In metadata capture template we could declare replicants, similarly to DCTs. When metadata for such tags is captured, it will look like long keys
(E.g. /Teamsite/Metadata/Blah/0/Identifier) - something that one would see when Data Deploy stores metadata ina DB.

Is anoyone familiar with any API, or any coming API to handle this similarly to what we could use when parsing DCRs (as the data structure is exactly the same).

I know of a few techniques to deal with this - one is to create an XML out of metadata on the fly and process it with XSLT. (or produce DCR-like XML and process it with TeamSite: Smiley Very Happy

CRNode). I am also looking to the standard ways of producing such an XML using iwmetadata CLT (I posted a separate question about this).

However, accessing the metadata using a kind of an API would be really helpful as we do not only process metadata but also validate mandatory metadata in the workflow.

Any ideas? has anybody implemented anything like this?

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Find more posts tagged with

Comments

psr

Greg,

As I found this today, posted by you quite a long back .. Did you go any further in this? I will be intersted in if you could grab (ow write ur own)cany API's on this if possible can I see the files.

! Thanks

Adam Stoller

in 6.5 -- perhaps 6.x - iwextattr has a '-x' flag that allows you to dump (with -l) or read/set (with -s) the EAs in XML format. -- then you can parse it with your favorite XML parse.

The DTD for the EA XML is:
<!DOCTYPE ealist
[
<!ELEMENT ealist (ea)*>
<!ELEMENT ea (key, value*)>
<!ELEMENT key (#PCDATA)>
<!ELEMENT value (#PCDATA)>
<!ATTLIST value encoding (text|hex) "text">
]
>

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Atok.source.zip

4359.pdf

gzevin

Adam,

it's there in pre 6.5 as well. However, it's nowhere near from what we need.

this is a sample of the output:

<ealist>
<ea>
<key>TeamSite/Templating/Encoding</key>
</ea>
<ea>
<key>TeamSite/Templating/PrimaryDCR</key>
<value>showcase/promobox.dcr</value>
</ea>
<ea>
<key>TeamSite/Templating/PrimaryDocumentType</key>
<value>swsiweb/promobox</value>
</ea>
<ea>
<key>TeamSite/Templating/PrimaryPT</key>
<value>promobox.tpl</value>
</ea>
</ealist>

as one can see, it's no more that key-value pairs in a different format. No good for what I need.

To answe the psr's question - no, I have not come up with anything yet (no time, as simple as that) and I find it really amazing as to why IWOV has not done something similar to, say, template-based e-mail, when they parse workflow XML with TPL API.

From what I saw in some of my clients, IWOV guys in Sydney have come up with a decent module that processes metadata using XSLT. I have just completed some changes to their XSLT stylesheet to make it work for very complex metadata. I guess, this module could be easily productised, if, say, product management contacts relevant consultants (I can provide the names to anyone intersted at IWOV).

finally, I find it really hard to believe that with so many implementations of TeamSite only a handful of people ask such questions...

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU