search

metarelate / metOcean-mapping

GNU Lesser General Public License v3.0
1 stars 6 forks source link

Flatten All Graphs into Single Data Pool (B) #5

Closed wizardstoy closed 11 years ago

wizardstoy commented 11 years ago

Examine loading all data into a single dataset rather than into separate graphs.

The is dependent upon GRIB data [#4]. This will also require a change within mapping-manager [metarelate/mapping-manager#6] for the new loading data and scripts.

With all the triples residing within a single data pool, queries will need to be carefully targeted in order to preserve current performance.

None

marqh commented 11 years ago

rather than flatten everything into one graph, potentially making the process for https://github.com/metarelate/metOcean-mapping/issues/10 remote end points more complex, I suggest using format specific named graphs

This has the same initial effect, that no status based graphs exist, meeting the design criteria that updates to records should not change existing records.

marqh commented 11 years ago

some flattening has occurred, but graphs will be kept for organisation, implemented in #17