I would agree with Guy on this.
If the (structured) data is stored in a database table, then even though
you imported a votable the first time, it wouldn't prevent you from
replacing the contents with data from a FITS file later.
Even if the FITS file contained different columns.
Use case -
I'm setting up a database by importing into vospace API on the database
system.
I accidentally import the wrong file the first time.
I should just be able to replace this by importing the correct file.
Dave
ps. Can we move the discussion back to the vospace list.
Matthew Graham wrote:
> Hi,
>
> When I create a StructuredDataNode (either through createNode or one
> of the import methods), the created node will have the <accepts> that
> the service sets:
>
> <node xsi:type="vos:StructuredDataNode">
> <accepts>
> <view uri="ivo://net.ivoa.vospace/views/tabular/votable-1.1"/>
> <view uri="ivo://net.ivoa.vospace/views/tabular/fits-table"/>
> </accepts>
> </node>
>
> When data of a particular format flows to this node, should the list
> of <accepts> views be cut down to just that of the input data?
> Input format is votable so should the node become:
>
> <node xsi:type="vos:StructuredDataNode">
> <accepts>
> <view uri="ivo://net.ivoa.vospace/views/tabular/votable-1.1"/>
> </accepts>
> </node>
>
> If I were then to attempt to update the data with a second import, I
> would be constrained to provide my data in votable format.
> Is this the behaviour we want?
>
> Cheers,
>
> Matthew
Received on 2006-08-03Z11:56:42