Storing header information to database

[Amergin]

I've a database where the graph represents a single dataset. Every node has multiple attributes, among one of them is a list of datapoints, and the list is stored as a single string, for example:

"-0.145612:-0.017787:-0.149197:0.019434:-0.030675:-0.018852:-0.059626:-0.123525:-0.085181:-0.095958:0.070881:-0.068942:-0.011469:-0.131096:-0.145013:-0.220525:-0.083212:0.012034:-0.040449:0.065762:-0.188752:0.002856:-0.059711:-0.012304:-0.106168:-0.088554:-0.024919:-0.211156:-0.077468:-0.077814:-0.099627:0.062143:-0.037822:-0.003117:0.119588:-0.321827:0.146043:0.018319:-0.116253:0.063670:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA:NA"

Every datapoint originates from a single source, for example the first datapoint could be from source1, second from source2 etc. These are all identical for the nodes.

Now the question is, how should this source information be stored in the database?
- Every node could have an attribute containing a list of the sources. I would then, however, wasting space since they are identical for all the nodes.
- I could create a single node that contains these, and link the node to every real data node. This doesn't seem very handy since if I want to access the sources directly I'd need to remember the node number or create an index containing the one node and do a wildcard query to it (which, according to the documentation is not advisable).

[Michael Hunger]

What about creating one node per data source and relating your nodes to the datasource and putting the actual value as property on the relationship?

Michael