"" Two of the Angolan varieties have gone by the outdated term ǃʼOǃKung (or ǃʼO ǃuŋ
o nthe flip side if anyone actually searches for "sekele" they get nothing
not that i'm against having two differnt types of seke or vasekela Bushman i nour language options...
you know what I mean here
i think we really, really for everyone involved need to limit this to a list of them ost commonly written languages. say maybe the top 200, 300 languages. and thne we can re-implement languages on demand
this is what musicbrainz does with the language dropdown on releases
i don't know how many languages there, but as a startingpoint we shoudl copy thre's. (s wel las include braille and sign languages)
but it in our documentation, and directly onto the page itself : if langguage you need is not in the list, please ask for it in [link] (so link to jira or a wikipage explaining how to do it)
BenOckmore has quit
monkey: for routes, i'm thinking of having new revisions for each entity ( edition, work...), and new revisions for adding relationship on them, does this sound sane to you?
this sounds more liek what mb does ? if it makes things more asy to see i definitly like it
I think that's a good idea Shubh. Once we have the ability to revert revisions, we will be happy to have a bit more granularity
For example we could revert adding the relationships without reverting the revision that creates an entity.
Yes, that all makes good sense
MRiddickW joined the channel
monkey: is it bad idea to create multiple entities asynchronously (parallelly)?, somehow i'm getting same bbid for each of them, any idea why that can be?
I'm surprised the BBID would be exactly the same. Did you confirm that by querying the database directly?
Agreed CatQuest this should come sooner than later
monkey: `new Entity()` producing model with the same bbid thus giving unique key error
Huh. Well that's new to me
Can I peek at the code you use to instanciate the Entity models?
Hey monkey, I've been thinking and I feel that I really want to go ahead with the project if allowed. I also think that it might not be a good idea to get started on it right away, as you will be busy with the other two projects and me just bustling in would defeat the purpose. Do you think it would be a good idea if I start working on it once
you're through with the meaty part of these two projects(I'm assuming somewhere around the end of July) or can you suggest some other timeline or any other suggestion with respect to how I can approach this