entity-level distribution information about lter-core-metabase HOT 4 CLOSED

technically, that's true. but I think you might need to have a distribution element of some type (I should confirm that).
One simple solution is a place holder that will obviously fail, like using http://example.org for the head. (pasta will ignore the URL if you upload from the web interface, so that is the only use-case this would work for)
another more true-to-life (or universal) solution might be appropriate, but will be more complex

from lter-core-metabase.

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
http://fake.url.placeholder.edu/
so that the next person who comes along and sees it does not just think it is broken.
Before committing to that, do test it with portal-s.
Also, isn't info about authentication (or lack thereof) included in the entity-level distribution tree? Or does portal just assume if that is not provided then to default to anonymous access? I like it to be explicit.

from lter-core-metabase.

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:
dataset-level access rules: control everything below the dataset node
unless
an entity-level access rule overrides it (and that rule only affects download of the entity it's with)

I think there is a longer discussion in the BP doc

from lter-core-metabase.

@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.

from lter-core-metabase.