0

Right now I'm writing up terms and their translations for this English to Urdu language in an excel sheet and what I'm concerned about to make data interchangeable.

Later one once I'm finished I might have a web service to JSON or XML from a mySQL database or from a nosql database.

My question is how to organize and write this information at this stage so I'd be able to transform and utilize this huge data into one of the above formats based on the need. Shall I keep writing in excel, or write stuff directly in a database (nosql I've no idea at the moment)

The app will be used on phones (iOS, android), desktop (mac/win) and a browser.

user2727195
  • 7,122
  • 17
  • 70
  • 118
  • You could finish up in an excel doc then write a script to read it in and insert it into a database since you already started in an excel doc. But I do recommend migrating to a database. It'll be easier to manage. – czifro Nov 17 '14 at 23:06
  • no problem, I've not done much but you mean I can start typing directly into a database? and that'd be better – user2727195 Nov 17 '14 at 23:37
  • Dbs do have interfaces to add data directly. MySQL often uses phpMyAdmin. Microsoft offers free software to manage DBs, which should allow the use of directly adding data without a query. – czifro Nov 17 '14 at 23:41
  • I can use mysql workbench, but my question now is, will this data be portable to nosql databases from there? – user2727195 Nov 17 '14 at 23:48
  • NoSQL structures data differently, so that might be difficult. If you are going to do a NoSQL DB in the end, I would just do it now. – czifro Nov 17 '14 at 23:51
  • well decision is neutral, if sql db is good for this kind of app (dictionary), I'll stick to it, do you think a data architecture/document for a dictionary app can be done in NoSQL, I'd pick it up (I'm not much familiar with NoSQL at the moment, have to study) – user2727195 Nov 17 '14 at 23:56
  • Though you would have to learn NoSQL, I would recommend using it since it is more of a document structure. Creating a relational structure for simple data might be a little to complex. If this answers your question, I'll post it as an answer so that this q can be closed. – czifro Nov 18 '14 at 00:01
  • yes, we are getting close, and you can post as an answer, last I believe dictionary app won't have a relation, just word and it's translation (unless I add synonyms etc.) but in your experience do you find using NoSQL doable and manageable for such app? – user2727195 Nov 18 '14 at 00:03
  • I'll be honest, I am most familiar with SQL and MySQL, but from my research, it seems doable and I would argue, more practical. MongoDB seems to be a good NoSQL DBMS. I'll post more in a answer – czifro Nov 18 '14 at 00:08
  • never mind, I've got my answer – user2727195 Nov 18 '14 at 15:49

1 Answers1

0

Most DBMSs have a way to input data directly using some built in interface, or external interface. I would move to a DBMS because it will be easier to manage your data. As for the type of DBMS, a NoSQL would be recommended, like MongoDB. This way the data will stay in a document oriented structure, which seems to better suit dictionary data. NoSQL converts things to JSON and stores that. So it should be very quick and scalable. This is my recommendation for a dictionary app. Good luck!

czifro
  • 784
  • 7
  • 24