Egeria connector #6080
Replies: 3 comments 1 reply
-
@smotornyuk thanks for sharing this 👍 I think DCAT extension is also for this purpose (not data but metadata). |
Beta Was this translation helpful? Give feedback.
-
Is this something like a client 'watching' a metadata and (optional: check for 'activities' and if something relevant has changed) then the clients (watcher) will pull the changes? |
Beta Was this translation helpful? Give feedback.
-
Perhaps we can do both... IRL, discovery, especially for public sites, means being indexed by Google. Maybe we should make DCAT a standard, built-in plugin as it supports schema.org markup and is supported by Google Dataset Search (GDS), especially now that GDS is out of beta. For finer-grained, more transactional metadata discovery and support of Data Exchange use cases where CKAN is used as an enterprise data catalog (beyond just publishing open data), it appears Egeria is better suited than DCAT. |
Beta Was this translation helpful? Give feedback.
-
As with any project, CKAN has a lot of bright sides and a few problems:) One representative of the latter group is data exchange between applications. There are three main tools available right now for this purpose, but all of them are CKANish and sometimes lack of abstraction prevents us from reaching farther places:
There is a tool designed exactly for this case, which standardizes the way of data exchange between platforms and can provide CKAN with abilities both to share data from other applications and take it from them. The one, mentioned in the title, Egeria
In simple terms, it just forms data-flow veins and CKAN(as well as any other application) can be connected to these veins and either inject its datasets into this body or pick some details from data-flow. The only two things we need to join this system is Open Metadata Repository Connector and a lot of enthusiasm
Beta Was this translation helpful? Give feedback.
All reactions