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

Make FGDC publicly available in S3 #96

Merged
merged 1 commit into from Jul 1, 2019
Merged

Make FGDC publicly available in S3 #96

merged 1 commit into from Jul 1, 2019

Conversation

gravesm
Copy link

@gravesm gravesm commented Jul 1, 2019

The FGDC file for each layer should be made public, regardless of
whether or not the layer itself is restricted. This adds a step during
the publishing process to change the ACL to public read on the FGDC file
as well as adding the necessary link to the file in the GeoBlacklight
record.

The FGDC file for each layer should be made public, regardless of
whether or not the layer itself is restricted. This adds a step during
the publishing process to change the ACL to public read on the FGDC file
as well as adding the necessary link to the file in the GeoBlacklight
record.
@JPrevost
Copy link
Member

JPrevost commented Jul 1, 2019

@gravesm I'm just confirming I understand this work. These files can be public even for private layers because it is just the metadata in these files? The restrictions are only necessary for the data layers?

@gravesm
Copy link
Author

gravesm commented Jul 1, 2019

That's correct. All the FGDC files should be public, even for restricted layers.

@gravesm gravesm merged commit c482c38 into master Jul 1, 2019
@gravesm gravesm deleted the fgdc-acl branch July 1, 2019 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants