upcoming IDP 3.4 Mapped AttributeDefinition

Losen, Stephen C. (scl) scl at virginia.edu
Thu Mar 22 08:45:37 EDT 2018

Hi folks,

Looking at the IDP wiki I see some changes coming to attribute-resolver.xml in 3.4.

I see that <Dependency ref="id"> is deprecated in 3.4 and replaced by <InputAttributeDefinition ref="id"> and <InputDataConnector ref="id">

I see that sourceAttributeID="id" is also deprecated in 3.4.

Will <AttributeDefinition xsi:type="Mapped" ...> continue to accept multiple input attributes, i.e., will it accept multiple <InputAttributeDefinition> child elements?

Currently I have several Mapped AttributeDefinitions that have multiple <Dependency ref=""> child elements.  These generate WARN logs in idp-process.log when they are processed.  Nevertheless, the Mapped attribute has reasonable behavior I think.  It strings together all the values from all the input attributes and performs the mapping on each of these values.

It would be very nice (for me at least) if "Mapped" in 3.4 continues to accept multiple inputs (and without complaint).  The wiki says that only the ScriptedAttribute and Template attribute accept multiple input attributes. I hope this is just an oversight in the wiki.

Do I need to submit a request for this feature?

Stephen C. Losen
ITS - Systems and Storage
University of Virginia
scl at virginia.edu    434-924-0640

More information about the users mailing list