-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to change phonology/morphology on SignBank #1219
Comments
@rosestamp the easiest is to remove the columns you do not need to update from the CSV file. Here is the file with the headers fixed and that lemma column removed. However, it still has capitalisation problems on some of the fields. (You will see this if you "import csv update existing gloss" on the updated file.) May I ask, how did you enter the data? I haven't seen this before without caps. Did the spreadsheet program do this? [I will see if I can revise the code to accept the choice field values also if the first letter is not a cap. |
IMPLEMENTATION CODE COMMENTS I found it!! I'm wondering why we didn't use this from the start? (Although I don't know if there is actually e.g., a difference in BACKGROUND https://github.com/iamoracle/django_case_insensitive_field The Tags model (prefab) is case sensitive as well. If you create new tags that differ in case, they are different tags. |
Hmmmm. The |
I revised the code to use iexact. @rosestamp: There is a field "Next-to" as a choice. It requires the hyphen. (You can use next-to now, without the cap. But the code is not yet live.) I'll put the revision up asap. |
@rosestamp there are also rows that update the same gloss. There should only be one row per gloss ID. (This is to prevent problems with conflicting updates in different rows.) You can sort the spreadsheet by Signbank ID to detect these. |
@rosestamp here's another one:
This needs to be a You could ask @ocrasborn if your research needs this to be different. |
@susanodd those kind of changes can come to me now :) There happens to be a difference between the > and the + categories. @rosestamp I will change downwards + contralateral/ipsilateral (which is a weird category anyway) to downwards + contralateral. |
Great! I have no idea what symbols are syntax or have semantics. Thanks. |
#1219: Case insensitive CSV input field choices, handshapes, semantic…
@rosestamp the CSV import is now case insensitive for the choice fields. |
@uklomp are there other fields where the syntax of the choice can vary? |
next-to and next to would be the same indeed. |
Like in the choices for e.g., Strong Hand:
... Do researchers use any other notation for the |
Ah ok, these could be spaces indeed. It's interchangeable.
From: susanodd ***@***.***>
Sent: woensdag 17 april 2024 13:07
To: Signbank/Global-signbank ***@***.***>
Cc: Ulrika Klomp ***@***.***>; Mention ***@***.***>
Subject: Re: [Signbank/Global-signbank] how to change phonology/morphology on SignBank (Issue #1219)
next-to and next to would be the same indeed. the ">"and + and / are not interchangeable in most cases. For the rest, I can't think of any examples where it matters. the underscore in names also doesnt seem very important, but which names do you mean? names of the fields?
Like in the choices for e.g., Strong Hand:
1_curved
Baby_beak
...
-
Reply to this email directly, view it on GitHub<#1219 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BDCXULFUXWOQGBQQYA7N3KTY5ZJUPAVCNFSM6AAAAABGFYOZQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRRGAYDGNZWGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Thank you. I updated 'next to' to 'next-to'. I understood that the other changes were made but maybe I missed something? When I enter it now, there are still multiple errors saying that the options for example "fingertips" for "location" are not found. Is there a more general problem I am missing? ![]() |
If you look at the page for uploading, there is a scroll bar where it shows a pull-down list of choices for each field. If the choices are in the pull-down, then it could be something with extra spaces or no spaces around the symbols? (I will check this.) If there are more than one that match, then that needs to be corrected in the system. (The names should be unique. But it could be that we didn't notice there are duplicates.) If none of those are the case, then there is something going on with the query search. (That would be a bug. There are choices where some are prefixes of others. So it could be that a prefix matches or something and it returns multiple instead of a unique result. It needs to obtain a unique choice.) The example choice lists are not sorted alphabetically, so this is also not good. (I'll fix that.) |
@rosestamp @uklomp It's Location |
@rosestamp another place you can see the existing choices for fields is on the It's Movement Direction |
Can i just ask if spaces matter between words like 'upwards' and > or + etc? |
It's because that's how they were defined when created by @ocrasborn. I shall add some additional parsing to allow them without spaces. (There can only be one in the list of choices in the interface, in order to allow searching. So internally they will be mapped -- after parsing away/adding back the spaces for the particular operations Is this also the case for the If you use a different interface language, you can also check what the translations look like for the field choices, to see if any of those are written differently in practice. (I can only read the English and Dutch.) At the moment, the CSV uses English for the values. If you need operators themselves (the |
@rosestamp I modified the code locally to also try to match the "+" and ">" with differing space. But for these, the feedback about not matching, they really don't match. (Some don't exist. Some have a Import CSV Update Existing Glosses
|
FYI
|
Hi @rosestamp. I can change or add options to the drop-down menus, but I'd like to do that only in cases where it is necessary, and not e.g. a mismatch with the available options. To go through the errors:
|
Thank you, I managed to solve all of the errors now so thank you for your help and for solving these issues. |
so, just to clarify, do I still need to look into the fields with > and + etc or did you find these as well? |
sorry, i didn't manage to keep up with all of the questions...what is the question about > and +? motivated form? |
For this one,
It should be "Motivated shape" (You can see the choices in the Import CSV update example pull-downs. Those are computed dynamically when you view the page.) |
See my last message with the bullet point list. I went through all the errors and described if we needed to do something about it, or if you needed change the input in the fields. Then you said you managed to solve everything, and my question is if this means I don't need to check things like 'backwards > upwards' for movement direction anymore. |
Thanks! so i think it's all resolved. Yes 'motivated' should have been 'motivated shape'. and yes, sometimes some < + combinations don't exist and if they don't, I guess they do need to be added. they are not interchangable. but it's possible that the combinations doesn't appear in NGT but does in ISL |
new_ISL_lemma_updates (1).csv
I am trying to upload this CSV in order to update existing entries on our ISL dataset with new morphological and phonological information.
When I try, using "Import CSV Update Existing Glosses", it states: Attempt to update Lemma translations. Use Import CSV Lemma Update instead.
When I do what it suggests using Lemma Update, it states:
The header row of the csv file looks like this: Handedness, Strong hand, Weak hand, Strong hand letter, Contact type, Location, Movement direction, Movement Shape, Relation between Articulators, Handshape Change, Repeated movement, Alternating movement, 42719, ISL, DUCK, 2s, B, no, , neutral space, to and fro, straight, next to, Yes, yes, 42687, DEER, W, beak2_open_spread, initial, forehead, forwards, arc, No
I do not understand what is wrong with my file.
Please let me know. Thanks!
The text was updated successfully, but these errors were encountered: