-
Notifications
You must be signed in to change notification settings - Fork 4
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
entity-level distribution information #29
Comments
technically, that's true. but I think you might need to have a distribution element of some type (I should confirm that). |
I had not considered the option of manually attaching the data files along with the EML to submit to PASTA. I've only ever done that for testing that feature itself. But yes I can see if you are working from your desktop not having a url-accessible file. I'll go with Margaret's suggestion but rather than example, Id make up a fictitious URL such as |
This issue is about entity-level URLs. so to talk about access rules, lets do it somewhere else. but to summarize access rules (since there is an access tree in the entity-level distribution, near the URL) this is the order of precedence: I think there is a longer discussion in the BP doc |
@gastil I think lots of smaller sites/projects use the manual upload option! At least all the EDI fellows not at UMich (OBFS and other sites) did AFAIK. |
On same topic as #26 item 11, what's the common usage pattern for entity-level distribution info?
Right now R code concatenates DataSetEntities.Urlhead and DataSetEntities.FileName to make a download URL. (I'm adding condition to return NULL if Urlhead is NULL.)
If unlike SBC, a site doesn't host data on own site, then perhaps there's no need for entity-level distribution in EML doc?
The text was updated successfully, but these errors were encountered: