Sp7 Data Entry: Prevent auto-insert of cataloger & catalog nr hash signs

Get Help
1

How can I prevent Sp7 to from automatically filling in the cataloger field with the user’s agent and also make it leave the catalog nr field empty, i.e. no pre-filled hash/pound signs?

I’ve tried removing and blanking the initialize attribute, but that doesn’t work:

    <row>
      <cell type="label" label="New Catalog Number" initialize="align=right"/>
      <cell type="field" id="1" name="catalogNumber" uitype="formattedtext"/> <!-- initialize="series=true" -->
      <cell type="label" labelfor="3"/>
      <cell type="field" id="3" name="accession" uitype="querycbx" initialize="name=AccessionCO;title=AccessionCO" isrequired="false"/>
      <cell type="label" label="Old Catalog Number" initialize="align=right"/>
      <cell type="field" id="14" name="altCatalogNumber" uitype="text"/>
    </row>
    <row>
      <cell type="field" id="yn1" name="yesNo1" uitype="checkbox" initialize="editable=true"/>
    </row>
    <row>
      <cell type="label" labelfor="4"/>
      <cell type="field" id="4" name="cataloger" uitype="querycbx" isrequired="true"  initialize="" /> <!-- initialize="name=Agent;title=Catalog Agent" -->
      <cell type="label" labelfor="5"/>
      <cell type="field" id="5" uitype="plugin" name="this" initialize="name=PartialDateUI;df=catalogedDate;tp=catalogedDatePrecision" uifieldformatter="Date" default="today"/>
      <cell type="label" labelfor="excoll"/>
      <cell type="field" id="excoll" name="text3" uitype="text" isrequired="true"/>
    </row>

image

2

Hi @fedoras,

  1. To remove the ######### (number sign, hash, or pound sign) that is automatically filled for auto-incrementing numeric fields, you can disable it from the Form Meta menu.

  2. At this time, Specify automatically sets the ‘Cataloger’ field to the current user’s agent (code on GitHub). This behavior is not configurable

    For now, you can use one of the other Agent fields on the Collection Object to capture the cataloger if the auto-fill behavior is undesirable. Consider using agent1 or inventorizedBy, as long as they are not already in use. Consider the impact on existing queries, exports, and other factors if you choose this route, as you will need to migrate the data to the other Agent field.