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 and FormAPI

guppy1

TeamSite 6, Win2k SP3

Hi, I've read that the datacapture.cfg for Metadata does not work with FormAPI. Given this constraint, how do I populate some text fields into the datacapture.cfg when it is first loaded? I cant use a cgi-callout as that would require some sort of user interaction. I need these fields populated automatically upon loading of the metadata capture form. Also, these fields need to be populated with some dynamic data such as the content author userid or the content filename and vpath.

Appreciate any help. Thanks.

Find more posts tagged with

Comments

Adam Stoller

Use a wrapper script around the CGI used for setting metadata - in the wrapper script run a bunch of iwextattr commands to pre-set some metadata - then when the metadata form is rendered, those values will show up pre-populated.

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

dataseteh.zip

gzevin

.. or, if the data is set once, one could use <default>

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

gsundeep

Hi,

Would you please suggest, if how can i validate a field within the metadata datacapture.cfg.
Will the wrapper script will do this job , since i have a field within my metadata datacapture.cfg that needs to be validated .The logic for validation is simple in that , i need to restrict users to enter a date in above mentioned field not more a year from the sysdate.

Please suggest possible solutions.

Thanks,
Sundeep

gzevin

validation regex will not do. I could think of either external task in the workflow, that wlill check for this and bounce back if the data is not kosher. This is the most suitable solution as the validation task will have to be written anyway... just to check whether mandatory metadata is set. Alternatively, I'd sugest a callout that alidates the date using javascript. I personally have not tried whether this will work for a readonly field. If it does, then this solution is also a candidate

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

Adam Stoller

... and of course there's always waiting for the next (or next-to-next?) release where the templating and metadata UIs are supposed to be merged tighter such that things like FormAPI will be able to be used on Metadata Capture forms... unfortunately that doesn't help in the here-and-now - so I think a cgi-callout may be the only way.

Unfortunately though, if you're using 6.0/6.1 - the only field you can reliably act on with a cgi-callout is the field directly associated with it - otherwise you could have a cgi-callout at the end of the form that ran validations on all the fields (there's a bug/feature request open on this which will hopefully be resolved when the UI engines merge).

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

gzevin

yep, Adam.. we keep repeating the same thing again and again and again

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

gsk

Hi Fish,

I am referring back to your statement: "Use a wrapper script around the CGI used for setting metadata". Could you please elaborate the exact steps involved in pre-setting value for a readonly field in the metadata capture capture form?

Our System is to be implemented on TeamSite 6.5.

Adam Stoller

Hi Fish,

I am referring back to your statement: "Use a wrapper script around the CGI used for setting metadata". Could you please elaborate the exact steps involved in pre-setting value for a readonly field in the metadata capture capture form?

Our System is to be implemented on TeamSite 6.5.

It's called: using iwextattr from within the wrapper script before (or after I suppose) you run the tagging UI.