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

Catalog Records #74

Open
valentinedwv opened this issue Jun 7, 2018 · 5 comments
Open

Catalog Records #74

valentinedwv opened this issue Jun 7, 2018 · 5 comments
Assignees

Comments

@valentinedwv
Copy link
Contributor

Feature:
Allow for the creation/linking of a catalog/source record to a harvest

Setup a link to that record

@pandzel-zz
Copy link

David,

I would like to understand what's your use case for that request; I can only presume that you would like to get records harvested into geoportal catalog and then provide a clickable URL on the search results individual record to the original record, right?

My problem is I have to generalize that functionality to fit all the protocols, but not all protocols would be able to provide that every time, for example what of the repository is CSW and it has to be POST request to access records, or what if repository has no concept of a record at all?

@mhogeweg
Copy link
Member

@valentinedwv could you elaborate? currently when harvesting into Geoportal Server Catalog, it knows that records came from the same source and from the same harvest task. Is that what you were looking for? or some other explicit link between harvested records?

@valentinedwv
Copy link
Contributor Author

Looking for a way to provide a more explicit link to a repository. Right now it is just a name.
Also, it would provide some additional context.
Use case.

  • explicit link could provide:
    ** link to the repository. If this is a aggregator, then this would not be in the record.
    ** thumbnail of org logo with a record.
    ** information on what has been harvested, and the sources, and when.

Part of the thought was the CKAN stores harvest information records, or at least makes them retrievable. This is not stored in a GPT, and it some form of a record was in the GPT, then it might be useful, and easier to add (where did this stuff come from, here is a list).

@mhogeweg
Copy link
Member

Currently we disconnected the harvester from the catalog. In part as we see users use the harvester without geoportal and vice versa. We are looking to update the UI of the harvester and to improve on the harvest reports (see #118 and #116). I think if we plan this right, we could make it so that the harvest can be run in a tab in the catalog app with aligning UI (similar to the map viewer). then if we think about this a bit more, the harvest reports could be pushed into the geoportal catalog and made searchable as one of the collections with its own facets (part of catalog plan). would that work for you?

@valentinedwv
Copy link
Contributor Author

Yes

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