Best practice to store data artifacts

What’s best practice for storing data artifacts? Currently we store them as csvs but I was wondering if pickling them makes more sense or if anyone has any experience with the pros and cons of doing that.

Hi @davidclarance , thank you for writing in with your question.

Artifacts are a versatile and expansive feature of our platform for your data versioning needs. We don’t have a ‘best practices’ guide as artifact use cases is unique to a users workflow. Our documents are extensive and highlight various use cases and examples of artifacts creation/logging, see here. Do you have a specific use case for wanting to pickle your csv file first?

Hi @davidclarance, since we have not heard back from you we are going to close this request. If you would like to re-open the conversation, please let us know!