[OCLAPI2] Design CSV Generation and Content Changes

OpenConceptLab / ocl_issues

Issues for all OCL repos. NOTE: Install ZenHub Browser Extension and request access to the OCL Roadmap board to view all issues and to contribute

4 stars 1 forks source link

[OCLAPI2] Design CSV Generation and Content Changes #597

Open snyaggarwal opened 3 years ago

snyaggarwal commented 3 years ago

Generation:

[ ] It should be async.
[ ] It should return all resources (and not limited).

Content:

[ ] It should not depend on django-queryset-csv package
[ ] It should take custom headers and values
[ ] It should include new core attributes (FHIR) for Source/Collection
[ ] It should include new mapping model attributes
[ ] Concepts CSV should include display_name in name column

snyaggarwal commented 3 years ago

@paynejd Created this ticket to track changes on CSV. Right now CSVs are missing the features listed above. Let me know if anything else needs to be added to this.

paynejd commented 3 years ago

@snyaggarwal is this using the same columns as in oclweb v1?

The changes you listed look good for the first pass. However, in the future, it would be better to provide the CSV export in a format that OCL accepted for bulk imports. We probably want to wait and do this in a future ticket though.

snyaggarwal commented 3 years ago

yes the columns are same as v1 for now!

paynejd commented 3 years ago

Cool- let's go with the changes you listed then and I'll create a ticket for modifications to the CSV export format in the backlog

On Wed, Feb 24, 2021 at 1:36 AM Sny notifications@github.com wrote:

yes the columns are same as v1 for now!

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/OpenConceptLab/ocl_issues/issues/597#issuecomment-784828711, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJCOON2MRXEEP27SGNW6N3TASM6XANCNFSM4X3ZVR3A .

paynejd commented 1 year ago

@snyaggarwal Is this ticket still relevant?

snyaggarwal commented 1 year ago

@paynejd It is still relevant, but might already be in v3 priorities to have better "CSV export" of content.