Describe the bug
When I supply my own metadata, I am unable to prepend my data with s3:/// in the documentreference content.url . It has to be file:///. Why?
To Reproduce
Steps to reproduce the behavior:
- Clone down any data project / remote add a file to a repo
- Change the content.url to be prepended with
s3:/// instead of file:///
meta validate
Expected behavior
Expected meta validate to pass and file to be downloadable after
Environment (please complete the following information):
- Version: 0.0.7rc22 (development at 2877cd5)
Additional context
Add any other context about the problem here.
Describe the bug
When I supply my own metadata, I am unable to prepend my data with
s3:///in the documentreference content.url . It has to befile:///. Why?To Reproduce
Steps to reproduce the behavior:
s3:///instead offile:///meta validateExpected behavior
Expected meta validate to pass and file to be downloadable after
Environment (please complete the following information):
Additional context
Add any other context about the problem here.