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

guidance on large Croissant files, especially in <head> #646

Open
Tracked by #163
pdurbin opened this issue May 6, 2024 · 0 comments
Open
Tracked by #163

guidance on large Croissant files, especially in <head> #646

pdurbin opened this issue May 6, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@pdurbin
Copy link

pdurbin commented May 6, 2024

Could the spec offer guidance on large Croissant files, especially when they are added to the <head> of a dataset landing page, greatly increasing its size?

This is not a new problem for us (Dataverse). To support Google Dataset Seach, we already include Schema.org content, which can be quite large, in the <head> of pages. A dataset with 25,310 files has a Schema.org file that is 4.4 MB, mostly due to the long file listing under "distribution".

Croissant exacerbates the problem. The same dataset yields a Croissant file that is 7.1 MB. This a lot of extra weight for a dataset landing page.

Can you please suggest some best practices? What is a reasonable upper limit for a Croissant file that will go in the <head> of a page? When we reach the limit, what should we do? Only show a few files under "distribution"?

Again, I'm mostly talking about the content that goes into the <head> of a page. A 7.1 MB Croissant file is fine when it is downloaded separately from the dataset landing page, via API.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants