Front end error when adding new forms to dictionary

[Gertrudius]

When trying to add the below forms to the dictionary through the front end I receive the following error. I'll go ahead and add them manually, but I wanted to make sure that there was a record of the error

e-zi-ba-ku-ni, ēzib+am+kum+ni, ēzibakkunni, G 3ms pret. subj.+vent +2ms dat. e-zi-ba-ku-ni, ezibā+kum+ni, ezibākunni. G 2mpl imv.subj.+2ms dat. e-zi-ba-ku-ni, ezib+am+kum+ni ezibakkunni, G 3s stative.subj.+vent +2ms dat.

[Gertrudius]

It seems like the issue might be specifically tied to the adding of properties, because after I added the forms manually, the front end threw a parse specific error when I tried to add the parse (though I assume this underlies the above one as well).

[Gertrudius]

To compensate for this in the meantime, I've created two stored procedures that can add form, spelling, and appropriate parse. You can use the below spreadsheet to see the shorthand for the parse string that the procedure reads, which mostly follows the value abbreviations where possible. It is also requires the parse elements to be ordered based upon their order in the properties taxonomy under the admin tab on the website, so keep that in mind as far as the order of parse elements.

NOTE: if the procedure fails to read the entire parse string, it will return all that was left of the parse string when the issue occurred, which can point you to the problem element.

https://docs.google.com/spreadsheets/d/17_P7DN6nympvO1RxT7sbm7sJMqnKg1QVtcuVxTIk8qY/edit?usp=sharing

add_form requires these components

• word_uuid: the uuid of the word the form belongs to
• form: the bound transcription version of the form.
• spelling: a single spelling that can be added along with the form. Leave the field as "" if you don't want to add a spelling.

It internally calls add_parse which needs these fields, otherwise, leave them as "";

• pos: part of speech to be added (see values under the top morphological form variable, ie. verb, noun, etc.
• this_string: add parse here, formatted with a period after each element, even the last one in the string. Use the website's taxonomy to determine the order that they should occur in, because the procedure logic follows that. ie. "finite_verb.G.prt.third.m.sg.ind." etc.

To just use add_parse you need these fields:

• form_uuid: the uuid of the form to which the parse needs added
• pos: see above
• this_string: see above

The parse procedure is finished and supports all of these word types for pos:

• Preposition (prep)
• Adverb (adv)
• Pronoun (prn)
• Adjective (adj)
• Noun (noun)
• Interjection (itj)
• Conjunction (cnj)
• Particle (part)
• Numeral (num)
• Verb (verb)