Hi @olisb no worries 😄
- When you use codes for values - i.e. in the Legal Form list why do you need the code? i.e. why do we need to use "L2" to represent a Co-op? Why not just store the value "Co-op"?
You actually have to use "Co-op" instead of the code L2 (i.e. don't bother with the code, use the name directly)
- Can I presume you never need / want to present the code value i.e. "L2" to a user...? So, if a Node Operator was making / updating their profile, for the "Legal Form" field you would want to present them with a drop down list of the options: Informal Group, Cooperative, Company, Non-Profit Organisation and Social Entreprise? (NB: "Social Entreprise." is spelt wrong on your Vocabs page) but return the associated L value in the JSON we present back to you?
Yes for the list, that would be brilliant, but it would need to show the the actual named values, e.g. Social Entreprise etc.. instead of the codes
"Social Entreprise." is spelt wrong on your Vocabs page"
thanks for the heads up!
- Why do you show a dot after Definition? Especially if you don't want it to be included...
I think it was a historical error that became a standard when describing the vocab in html, we will patch it up 🙂
- What do you expect / want to happen if someone wants additional options for a field - i.e. they would like to add charity which is a profit making entity?
At this point they would need to ask us to make that field for them. Our idea currently is to create a specified vocabulary that allows initiatives to describe themselves in a more uniform manner (rather than allowing them to describe themselves freely)
We use the URL as the unique ID - so would that be ok in the ID field (as well as the URL field)?
That seems sensible
Golly, now you're asking! I'm not sure... we have quite a bit of work to do first... but I would like to think it will happen before xmas...
OK, if you need support feel free to contact us!