AusDTO / disco_layer

Code, outputs and Information relevant to the discovery layer.
1 stars 5 forks source link

normalise service catalogue and sync to RDBMS #45

Closed monkeypants closed 9 years ago

monkeypants commented 9 years ago

this is WIP ATM.

monkeypants commented 9 years ago

re: Services (not including Dimension). So far, done:

not yet done:

Unsure about:

monkeypants commented 9 years ago

probably should also be recording agency!

monkeypants commented 9 years ago

Still TODO:

monkeypants commented 9 years ago

@nokout, unless I'm labouring under a silly bug, it's NOT the case that the combination of agency and serviceID are unique. For example, it seems that DVA has 7 services with ID of "SVC_002" (Run That Town, Before The Storm, Hazardous waste permits, PTSD Coach Australia, TrackMyGOALS, ACCC Shopper app, Trove).

So we are back to using names as the unique identifier... which means that names can't change. Or we are back to using the .json, which contains the name so has the same constraint.

Unless, SVC_002 is an anomaly and I'm right to reject it? please advice.

monkeypants commented 9 years ago

Ha! my bad. When I added the "agency" foreign key to an existing table, I had to give it a default foreign key... of 1... which is DVA. Truncating the tables (then repopulating them from the json) fixed it.