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; } } }

read only fields tagger gui

kellyrmilligan

Wasn't sure which forum to put this in. We are configuring metadata capture screens for our dcrs. We are pre-populating some of them such as author, creation date, etc. In a regular dct I could do some formapi and set these to be display only so that the users could see the value, but not change it. How can I do the same in the tagger gui?

Thanks,
Kelly

Teamsite 6.1, Solaris

Find more posts tagged with

Comments

Adam Stoller

As I responded in the other forum where you posted this - you should be able to use the same technique as you do in regulard FormsPublisher DCTs - take a look at IWHOME/local/config/metadatacapture6.0.dtd for reference information.

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

Ebe

I apologize if this has been answered in another forum and my reply to this post is really a further question.

I am a very new user to TeamSite and am learning to code metadata capture forms (we haven't got to MetaTagger yet). I have worked out how to get an item to be readonly and these fields are be prepopulated from our dcr. Does anyone know if and/or how I could grey out these items so they do not look like input boxes?

Thank you,
Ebe

Deakin University
Australia

Adam Stoller

Unfortunately, metadata capture forms do not [yet] support FormAPI - as such you do not have the kind of flexibility for manipulating the visibility or active/inactive abled/disabled qualities of fields as you do in TST / FormsPublisher datacapture forms. So I think for now, if your using a metadata datacapture form your limited to the readonly or hidden qualifiers pretty much.

I *think* the *next* release of TeamSite (6.7? 7.0?) is supposed to have a revamped datacapture form UI so that *both* templating and metadata capture will use the *same* rendering engine and thus you will be able to use FormAPI (or whatever succceeds it?) for *both* kinds of datacapture forms ...

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

kellyrmilligan

This is exactly what I am trying to do as well, I have some fields that I am pre-populating, and when a user hits file->tag, I want them to see the values that I pre-populated in the field, but not be able to change them. I think what you are saying is that I can't do that at the moment, right?

or if I use the read-only tags, will that do the trick? I am not too concerned about if the input style box is rendered or not, although if would be nice if it rendered the same as formspublisher.

kellyrmilligan

sorry to ask this, but would it be possible to post a code snippet for what you have that is working for the read-only part?

Adam Stoller

If you are pre-setting the values with iwextattr - then I believe you can have the DCT define the field as being readonly and it should do [essentially] what you want. The rendering may be less than ideal, but you should have a value showing up in the metadata capture form that the user can see but not edit.

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

kellyrmilligan

Here is the code I have tried, I am not sure why it is not working..

<item name="CREATIONDATE">
<description>Date format is YYYY-MM-DD</description>
<label>Creation Date: (YYYY-MM-DD)</label>
<database deploy-column="t" searchable="t" data-type="datetime" data-format="yyyy-MM-DD"/>
<text maxlength="10" size="10" validation-regex="^[0-2][0-9][0-9][0-9]+-[0-1][0-9]+-[0-3][0-9]" required="t">
<default>$currdate</default>
</text>
<readonly/>
</item>

The manual is less than helpful, as always.

So when I hit file-> tag, I the field is pre-populated, but I can still edit.

Johnny

reading the metadatacapture6.0.dtd shows that readonly falls under the item tag, so you would replace your text field (as that is an editable field) with readonly.

IE


<item name="CREATIONDATE">
    <description>Date format is YYYY-MM-DD</description>
    <label>Creation Date: (YYYY-MM-DD)</label>
    <database deploy-column="t" searchable="t" data-type="datetime" 
                      data-format="yyyy-MM-DD"/>
   <readonly>$currdate</readonly>
</item>

John Cuiuli

kellyrmilligan

that works, thanks. is there a reason the value only shows up if you set it via clt? my original inline got some of the values in perl via env variables, but to do read only do we need to pull from dcr, and set ea's in a cgi /callserver type scenario?