Jayanth, I wanted to just add a bit more background to Ryan's answer. A big part of the Import/Export task will be to make it easier for Cultural Heritage organizations to move their data into Arches. Right now, most CH organizations seem to be comfortable working with spreadsheets, Access databases, or perhaps more traditional relational databases. The goal of this task is to simplify the task of mapping data fields from more traditional data store (such as csv or relational database) to nodes on Arches' resource graphs.
As for your question on the RESTful API. I agree that this would be very valuable and an excellent idea to pursue. Cheers, Dennis On Tuesday, March 4, 2014 1:44:14 AM UTC-8, Jayanth Koushik wrote: > > Hi! > > I have a few questions regarding the idea about 'Import/Export > Improvements'. > > - The ideas page says 'The goal of this project would be to develop a > module (preferably in python) capable of traversing a fully populated > Arches resource graph (json)and writing its information out to a more > widely used data exchange format (xml, kml, rdf, shapefile, etc.)'. But > isn't JSON a standard data exchange format already? Why convert it to > something else? > - Does Arches expose a RESTful API? If not, would implementing that be > something that could be incorporated into this project idea? > - What portions of the source code are relevant to this project? I > wanted to get a better idea about the existing import/export > functionalities and the arches resource graphs. > > Thank you > > Jayanth > -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
