<accessCondition> doesn't allow a value #119

Closed
JenniferMartin opened this Issue Jan 16, 2013 · 0 comments

Projects

None yet

3 participants

@JenniferMartin

In MODS, is a single level element and thus should have a value node when created in the crosswalk. It doesn't. You can add attributes to it, but you can't actually assign a value to it.
accessConditions problem

@mdaines mdaines pushed a commit that referenced this issue Jan 24, 2013
@daines daines Change AccessConditionDefinition in the MODS model so that it descend…
…s from XsString rather than ExtensionDefinition, and ensure its attributes are consistent with the MODS schema. This fixes that the <accessCondition> element would not accept text input in the crosswalk interface (#119).
9fa6cbe
@mdaines mdaines pushed a commit that referenced this issue Jan 28, 2013
@daines daines Revert "Change AccessConditionDefinition in the MODS model so that it…
… descends from XsString rather than ExtensionDefinition, and ensure its attributes are consistent with the MODS schema. This fixes that the <accessCondition> element would not accept text input in the crosswalk interface (#119)."

This reverts commit 9fa6cbe.
383cc6b
@mdaines mdaines was assigned Jan 30, 2013
@gregjan gregjan closed this Mar 19, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment