-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eml2eal() should import size, md5checksum, number rows, and download URLs #110
Comments
A function Currently, the only hang up is handling the quote character field (") which causes the output table to collapse. |
@clnsmth so far I think the best representation is to always have an escaped quote character (i.e. |
Yeah @kzollove, quote characters are a bit challenging here, especially in and out of a spreadsheet editor. The current template_physical() plays nicely with make_eml() but is not optimal (see the docs for Ultimately physical.txt should return unscathed from the round trip of |
* Create phyiscal.txt as part of eml2eal In order to create EML from web-hosted entities, a mechanism is required for providing the physical information required to fully describe entities. This function does the reverse of that, creating the physical.txt template from an EML file. This function will be useful in an instance of updating a data package with large entities as the editor will not need to download the large entities. * Add entity URLs during eml2make_eml * Fix the quote character issue The utility function write_templates would not output a table correctly due to the quote character. Manually write to table using same functionality but with quote parameter set to 'auto'.
This would enable best possible transfer from ezEML to EAL with minimal data loss.
My particular situation is that I'm trying to migrate metadata created in ezEML with 72 tables to EAL. If the above parameters were passed to make_eml(), there would be no need to ever physically download the data tables (that are currently in ezEML and have static download links)
Download example ezEML data package here
Is this too specific of a use case? Could play nicely with #107
The text was updated successfully, but these errors were encountered: