ediorg / ezcatalog Goto Github PK

I get an Error popup that says "There was an error making the request." when trying to access the search. It occurs on my site Arctic LTER and the live demo.

After changing the filter query (Steps 3 and 4) and running build_catalog (Step 5), the Live Demo page still shows data packages from Archbold Field Station and not data packages from the new query.

Hi @clnsmth,
We're integrating the ezEDI into the AND's css and I am unable to find the font-size adjuster for the standard search "search" button. Is there a way to increase the size of this button?

re: work in progress: https://andrewsforest.oregonstate.edu/data/streaming/other-stations/ezedi-data-catalog

When a forked repository is renamed from ezCatalog the live Demo.html and the iframe link will not have the correct repository name.

To solve this issue I edited build_catalog.yml to include
sed -i 's/ezCatalog/${{github.event.repository.name }}/g' README.md

Jim Laundre

Hi there,
Just forked the ezCatalog and love it! Running the Andrews data as a live demo. I'm trying to modify the advanced Search form to show by default. I've made a few changes to the form input in the demo.html but haven't been successful - do you where the controls are for this? Thanks again for sharing this nice work.

Configuration parameters such as pagination are set outside of /public/pasta.js and /harvester/pasta_harvester.mjs'. That way, commits to pasta.js` can purely be about improving functionality rather than changing settings.

That can be done in a script that calls pasta.js if the window.onload function in pasta.js was replaced with a regular function definition, and then the calling function (either in a separate script or inline in the HTML) would modify settings as desired (either inline or from a config file) and call the function to initiate the catalog.

Example queries listed under the Usage for Your Site section of the repository README serve the 3 most typical use cases we encounter. However, edge cases requiring more advanced filtering can be supported. Such edge cases should be demonstrated as a 4th point under the "Construct a filter query" step in the Usage for Your Site section.

It's very likely that users of the EDI Repository have data archived else where. Consider extending the scope of ezCatalog to provide users a single interface for showcasing their data.

The user would define the geographic coordinates within which to search.

As it is written, the build_catalog workflow creates a new branch 'master' instead of updating 'main' branch.

I assume this is not intentional, but if it is, should be mentioned in the instructions.

This is not currently indexed by /harvester/pasta_harvester.mjs.

Just want to drop this idea here since it relates to how these search results are returned and clicked on by users. Thanks again for sharing this code. I've always been fascinated how Google search has transformed the sharing of information.

from: https://seekingalpha.com/article/4497322-google-is-flourishing

In I'm Feeling Lucky, it is revealed what happened after Google beat out Overture for the AOL contract in May 2002. Google engineer John Bauer increased clickthrough 400% by adding code such that the keyword in the ad tied to the search phrase was changed to bold:

By the end of the contract's first year, we were far above the highest projections. Part of that success may have been attributable to a small shift made by an enterprising engineer. The day after the deal went live, John Bauer added code that boldfaced the keyword a user had searched for when it appeared in an ad, making it obvious that the ad was relevant. That single improvement increased clickthrough rates by four hundred percent. One engineer. One change. Four hundred percent.

[I'm Feeling Lucky Kindle Page: 304]

Currently, this button resets the LTER Core Area and Creator field, but does not reset the Year, Taxon, or Location parameters.

Not sure if this is intentional or not.