Go to the U of M home page
School of Physics & Astronomy
Assay and Acquisition of Radiopure Materials

User Tools


universal_data_base:130320

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
universal_data_base:130320 [2013/03/20 17:50] – [Minutes] cooleyuniversal_data_base:130320 [2013/03/20 17:53] (current) cooley
Line 24: Line 24:
   * Hamilton Scholar event is next week.  Dr. Cooley will contact Phyllis Payne to get poster board.  We will meet in the lab next week at 5 pm for a quick meeting before we go over.  Dress code - suit.   * Hamilton Scholar event is next week.  Dr. Cooley will contact Phyllis Payne to get poster board.  We will meet in the lab next week at 5 pm for a quick meeting before we go over.  Dress code - suit.
   * Matthew was not able to attend.  However, he sent a report.  He has finished the json documents for the EXO data.  Dr. Loach is checking them.   * Matthew was not able to attend.  However, he sent a report.  He has finished the json documents for the EXO data.  Dr. Loach is checking them.
-  * ILIAS data import.  Ben hasn't had time to work on the import.  He hasn't run into any major issue yet.  One thing to note is that not all the files are in the same format.  The data seems to fit into 4 different csv files (ie 4 formats).  Ben is writing a bash script for importing the csv files.  Ben wants to know where to upload the data to - should we do it on a local installation and then at some point upload to cloudant.  Email Dr. Loach about how/when to upload to cloudant.  +  * Ben hasn't had time to work on the ILIAS data import.  Ben plans to get back to work on this Friday.  He hasn't run into any major issue yet.  One thing to note is that not all the files are in the same format.  The data seems to fit into 4 different csv files (ie 4 formats).  Ben is writing a bash script for importing the csv files.  Ben wants to know where to upload the data to - should we do it on a local installation and then at some point upload to cloudant.  Email Dr. Loach about how/when to upload to cloudant.  
   * Poster we are waiting for Dr. Loach to get back to us with the outline.   * Poster we are waiting for Dr. Loach to get back to us with the outline.
   * There is a new project for Keith which is to fix the search engine.   * There is a new project for Keith which is to fix the search engine.
   * Adam could not attend but sent an email with his updates.  The JSON schema specification has been encoded and in the repository. Instructions in Python on how to use this have been provided. The next step is to implement some javascript to require that any data sent to the database conforms to this schema. The best way to accomplish this, to ensure that absolutely any data sent to the database follows our specification, would be to implement this in the _design doc's 'validate_doc_function'. Cloudant recently implemented support for CommonJS, which means that we can import modules, such as JSV (https://github.com/garycourt/JSV) into the valdate_doc_function and use it to ensure that all docs follow the schema.    * Adam could not attend but sent an email with his updates.  The JSON schema specification has been encoded and in the repository. Instructions in Python on how to use this have been provided. The next step is to implement some javascript to require that any data sent to the database conforms to this schema. The best way to accomplish this, to ensure that absolutely any data sent to the database follows our specification, would be to implement this in the _design doc's 'validate_doc_function'. Cloudant recently implemented support for CommonJS, which means that we can import modules, such as JSV (https://github.com/garycourt/JSV) into the valdate_doc_function and use it to ensure that all docs follow the schema. 
  
universal_data_base/130320.1363819833.txt.gz · Last modified: 2013/03/20 17:50 by cooley