Did some updates to Pacific Asian site, on MK's instructions. I think more might be coming; there are other files in the dev site which are newer than those on the live site. Wrote for instructions on this.
BS working for JP reports a problem connecting from his php to the mysql db. He's using a line like this:
$db_url = 'mysql://username:password@host/databasename';
I've never seen that convention before. I'm used to four separate variables which are then passed into a mysql_connect call. I had no problems connecting using the more conventional approach, so it has to be something to do with his specific setup or code. Had a number of back and forth emails.
Some user feedback reminded me that the problem of the disappearing KEBI dictionary was never solved for the Indonesian website glossary (we had originally linked to the KEBI dictionary so that users could find words not in our simple glossary, but KEBI disappeared). I've now changed this to point to the Google translator, which works fine.
Finished javascript code in 8processOneToManys.html and make_inserts_from_csv.seq.xml
8processOneToManys.html now generates two outputs:
- the first contains sql comments on cross-reference and keywords that point to non-existent values, then sql statements to clear all records out of the four intermediary tables, then sql statements to populate those tables again
- the second returns the tab-delimited input, but in the cross-reference and keywords fields, only those values which are illegal remain, so it is easy to see where the problems still lie. That output (saved in the file 9_tabs_id_clean.txt) becomes the input for the last step in the Text Transformer.
make_inserts_from_csv.seq.xml is an instruction file used by the Text Transformer. It is designed to take as input 9_tabs_id_clean.txt and produce the sql statements to clear all records from the main table and then repopulate the main table again.
Am now waiting for BI to provide data with identified errors corrected.
If BI adds any new records to the lookup sheets (e.g. new keywords), then those will have to be added manually to the appropriate table in the database and to the javascript code in both the files mentioned here.
Full procedure to go from BI's spreadsheet to the sql files ready to populate the databases is in the file howto_xls_strings_to_sql_inserts.txt. It's kind of rickety and hands-on, but shouldn't have to be executed very often.