[Neo4j] Best practise for multi language properties
Best Practice for multilanguage properties Just a few month I am working with neo4j. We are modeling graphs for new Applications combining ontologies and data for production data. The most important thing actually is to have multi language properties for nodes and relations with the following most important use cases: - language amount of each node could differ, this means that node 123 could have EN and DE and node 234 EN and SP. - it should be possible to have a simple update process, like language packages, that we can fire to the graph Are there any best practices, base concepts or contacts to solve this? ... Thanks and regards from Regensburg-Germany, Ottmar ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Best practise for multi language properties
You mean something like internationalization? I don't know if that itself is a responsibility of the datamode/graph. You could probably use string arrays to store those. Or do you mean multi-language property names? Cheers Michael, Dresden,Germany Am 07.10.2011 um 09:24 schrieb Moootron: > Best Practice for multilanguage properties > > Just a few month I am working with neo4j. We are modeling graphs for new > Applications combining ontologies and data for production data. > > The most important thing actually is to have multi language properties for > nodes and relations with the following most important use cases: > > - language amount of each node could differ, this means that node 123 could > have EN and DE and node 234 EN and SP. > - it should be possible to have a simple update process, like language > packages, that we can fire to the graph > > Are there any best practices, base concepts or contacts to solve this? ... > > Thanks and regards from Regensburg-Germany, > > Ottmar > ___ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Best practise for multi language properties
Property names can have special characters in them, so we use a pattern like: Description Description.EN Description.DE This way we can keep any number of localiz(able) expressions on a node. Based on the user's language, we first try to get the value in the local language, then the default. -Original Message- From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On Behalf Of Michael Hunger Sent: Friday, October 07, 2011 8:07 AM To: Neo4j user discussions Subject: Re: [Neo4j] Best practise for multi language properties You mean something like internationalization? I don't know if that itself is a responsibility of the datamode/graph. You could probably use string arrays to store those. Or do you mean multi-language property names? Cheers Michael, Dresden,Germany Am 07.10.2011 um 09:24 schrieb Moootron: > Best Practice for multilanguage properties > > Just a few month I am working with neo4j. We are modeling graphs for new > Applications combining ontologies and data for production data. > > The most important thing actually is to have multi language properties for > nodes and relations with the following most important use cases: > > - language amount of each node could differ, this means that node 123 could > have EN and DE and node 234 EN and SP. > - it should be possible to have a simple update process, like language > packages, that we can fire to the graph > > Are there any best practices, base concepts or contacts to solve this? ... > > Thanks and regards from Regensburg-Germany, > > Ottmar > ___ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Best practise for multi language properties
Both possibilities we thought about. Using special characters like description.de is a good idea. Actually in one of our prototypes we have a global array language=(de,en,sp,...) and the properties are arrays where the values have the same order, so we could parse the responsed REST Object into a JSON object, which we could use as a view model object for the GUI. But the properties have most of the time empty fields. ... we are not happy about that. Ottmar Am 07.10.2011 um 14:19 schrieb Rick Bullotta : > Property names can have special characters in them, so we use a pattern like: > > Description > Description.EN > Description.DE > > This way we can keep any number of localiz(able) expressions on a node. > Based on the user's language, we first try to get the value in the local > language, then the default. > > > > -Original Message- > From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On > Behalf Of Michael Hunger > Sent: Friday, October 07, 2011 8:07 AM > To: Neo4j user discussions > Subject: Re: [Neo4j] Best practise for multi language properties > > You mean something like internationalization? > > I don't know if that itself is a responsibility of the datamode/graph. > > You could probably use string arrays to store those. > > Or do you mean multi-language property names? > > Cheers > > Michael, Dresden,Germany > > Am 07.10.2011 um 09:24 schrieb Moootron: > >> Best Practice for multilanguage properties >> >> Just a few month I am working with neo4j. We are modeling graphs for new >> Applications combining ontologies and data for production data. >> >> The most important thing actually is to have multi language properties for >> nodes and relations with the following most important use cases: >> >> - language amount of each node could differ, this means that node 123 could >> have EN and DE and node 234 EN and SP. >> - it should be possible to have a simple update process, like language >> packages, that we can fire to the graph >> >> Are there any best practices, base concepts or contacts to solve this? ... >> >> Thanks and regards from Regensburg-Germany, >> >> Ottmar >> ___ >> Neo4j mailing list >> User@lists.neo4j.org >> https://lists.neo4j.org/mailman/listinfo/user > > ___ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > ___ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
