Skip to content
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

No test cases have <access type="discover"> blocks #3

Open
atz opened this issue Nov 20, 2014 · 2 comments
Open

No test cases have <access type="discover"> blocks #3

atz opened this issue Nov 20, 2014 · 2 comments

Comments

@atz
Copy link
Contributor

atz commented Nov 20, 2014

This would be considered an error in production. We should decide how we want to behave if given such data and most test cases should be updated to include an <access type="discover"> block.

@atz atz changed the title No test cases have <access type="discover> blocks No test cases have <access type="discover"> blocks Nov 20, 2014
@jmartin-sul
Copy link
Member

FWIW: i see lots of <access type="discover">-related testing in spec/index_elements_spec.rb.

but that's just testing the index_elements stuff. what other behavior should be tested that's not getting tested at the moment?

@LynnMcRae
Copy link

Per conversation with John, the indexing logic would show the inconsistency (the error I think Joe refers to) by showing the object was declared both dark (per access=discover) as well as world/stanford/etc per access=read. This might initially alarm a collection owner who thinks their collection is all dark, but good that it would expose the contradictory data. We don't have any exposure issue here since the access=discover block determines if the PURL exists at all; any expression of object access after that would be meaningless as there would be nothing there to apply it to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants