To follow the separation pattern between content deposits and metadata-only deposits, we need two columns.
The reason we are using two columns is for a future use case where the origin of source code and the origin of metadata in a single deposit is different.
the column should be called metadata-provenance and should be populated with the value in the atom xml under the compatible property.
I don't think we need this new column, the information is already available in the Atom document
I don't think we need this new column,
Implementation detail on how the backend should compute the information (either once by populating this new column or parsing when needing the associated metadata file).
the information is already available in the Atom document
*will be*.
@moranegg You should care about the actual need which ttbomk is that information should properly be displayed to the user via the ui (you should not care how the backend store it).