You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently infobox properties are presented as string even though they might be of various types such as Integer, Float or Currency etc. This can be changed to make the information presented more richer and meaningful.
For example we can use rdf types (xsd:integer, currency etc). We can flatten some properties into a single property such as (birthDate, birthPlace, birthYear etc).
Example: San Francisco (screenshot attached)
The UTC Offset Property displays −7 even though it should display -7
The text was updated successfully, but these errors were encountered:
Hi @ram-g-athreya, if this issue is still open then maybe I can work on to fix this. This issue can be resolved with parsing and pattern matching for different types.
I am already neo4j certified professional, java content writer at Baeldung and a backend developer. Feel free to let me know if I can work on this.
Presently infobox properties are presented as string even though they might be of various types such as Integer, Float or Currency etc. This can be changed to make the information presented more richer and meaningful.
For example we can use rdf types (xsd:integer, currency etc). We can flatten some properties into a single property such as (birthDate, birthPlace, birthYear etc).
Example: San Francisco (screenshot attached)
The UTC Offset Property displays −7 even though it should display -7
The text was updated successfully, but these errors were encountered: