Import attributes table #24

Activity

1. ANAMASGARD commented on Apr 20, 2026

   

   ANAMASGARD

   on Apr 20, 2026

   Contributor

   More actions

   Sir @dlebauer, I’d like to work on this issue please could you assign me this , Thank You .
2. ANAMASGARD commented on Jul 16, 2026

   

   ANAMASGARD

   on Jul 16, 2026

   Contributor

   More actions

   Hi @dlebauer,

   I investigated the repository and the available BETYdb public API before starting the implementation.

   At the moment, the betydata repository does not contain an attributes.csv file, and the public BETYdb API does not appear to provide the contents of the attributes table. Because of this, I cannot inspect the real data or safely decide how it should be imported.

   Could you please guide me on the next steps needed to complete this issue end to end?

   Specifically, could you provide one of the following:

   1. An approved export of the attributes table, or
   2. A read-only database/dump containing the table, or
   3. The SQL query or official process that should be used to export it.

   It would also be helpful to confirm:

   • How we should determine whether an attribute belongs to a public record.
   • Whether the exported column should be named container or container_type.
   • Whether unmatched attributes whose parent records are unavailable should be excluded.
   • Whether you would like me to first post an investigation report before implementing the import.

   Once the source data is available, I plan to:

   1. Review the rows, containers, JSON structure, ID ranges, duplicates, and unmatched parent records.
   2. Determine whether the data is useful and safe to publish.
   3. Propose the best storage design.
   4. Get your confirmation on that design.
   5. Implement the import.
   6. Update the documentation, tests, and metadata.
   7. Run the complete package test and check suite.

   I have not made any code changes yet because I do not want to invent data or make assumptions about the correct import design.

   Thank you.