Metadata fields for data source columns #440
Replies: 13 comments
-
We've already got Would these change frequently enough to justify creating a new export, edit, import feature? |
Beta Was this translation helpful? Give feedback.
-
Is the metadata not stored in a table. If not shouldn’t it be? If it is, isn’t csv export and import relatively trivial? I think most of our tables could do with better metadata. If so, where is the easiest place to work on this? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I think we do need a details field. The description should contain a simple summary and the details the small print. Could that form be moved out of the admin so that more people could access it? |
Beta Was this translation helpful? Give feedback.
-
I would prefer just to give admin access to the folks we think would need to edit it. A typo in the "source_name" of the column description would break the operation of the query builder for those sources. |
Beta Was this translation helpful? Give feedback.
-
But the people who need to work on the metadata shouldn’t have admin access. Is there a way of protecting some fields after creation? |
Beta Was this translation helpful? Give feedback.
-
Yes, we could make some fields read-only in the admin interface. But before we code a technical solution to this, do you think that people who work on metadata could make their required changed directly to the CSV? And we just re-upload the CSV periodically when there are sufficient changes? |
Beta Was this translation helpful? Give feedback.
-
I thought that is what I suggested in the first place?? |
Beta Was this translation helpful? Give feedback.
-
I thought you were asking for a dedicated feature of the website where users could re-upload updated metadata. Right now the CSV is a part of the Django side of the data, not the DDW side, so the existing import/update form that @edwinmp created would not work for users to export and re-upload the CSV at will. Changes would need to be made to the CSV, committed to this repository, and then deployed. |
Beta Was this translation helpful? Give feedback.
-
It doesn’t make sense for database metadata not to be in DDW. Can the form not read and write to a DDW table? |
Beta Was this translation helpful? Give feedback.
-
Yes, the form can read and write to DDW tables. The new feature required here would be reconfiguring the system to read from an un-managed table for all of the column names and definitions. Everything is in one database. Tables managed by the Django object-relational mapping (ORM) are in the This would be a sizable refactor, but we can do it if we think it would help streamline our processes. |
Beta Was this translation helpful? Give feedback.
-
This is worth a proper discussion. Personally I think this is very important in the long run, but not perhaps urgent now compared to other priorities. |
Beta Was this translation helpful? Give feedback.
-
@bill-anderson I wonder if this is a discussion that we need to have again so this can be prioritised or we decide that we are not doing it. I'm going to make it is discussion for now until we can agree what work we want to take forward. |
Beta Was this translation helpful? Give feedback.
-
For each column in a data source we need:
Is it possible for this to be in a table that one can export, edit and re-import?
Beta Was this translation helpful? Give feedback.
All reactions