Open stefanprobst opened 6 months ago
see below re. first point. Should I go for baserow addition instead? Or better to stop updating baserow? some countries do not have a representation yet in the Marketplace.
thanks! no need to update anything in baserow!
are dariah member country actors always listed with role "reviewer"?
one tool/service tagged with "DARIAH resource" is not connected with a specific country: https://marketplace.sshopencloud.eu/tool-or-service/VZRMmh
are dariah member country actors always listed with role "reviewer"?
yes
one tool/service tagged with "DARIAH resource" is not connected with a specific country: https://marketplace.sshopencloud.eu/tool-or-service/VZRMmh
this can indeed happen. In that specific case, it is a tool developed by a dariah-eu employee, but we are waiting for more cases, from the dariah working groups for example. Resources part of the dariah network but not affiliated to any country specifically.
regarding the last question in the initial comment on how to distinguish between services and software. All software should be tagged with the "Software" value in the resource-category
property field. See for example:
https://marketplace-api.sshopencloud.eu/api/item-search?d.resource-category=%22Software%22&f.keyword=DARIAH%20Resource
There will probably be inconsistencies with what we have in the portfolio/database. And I was counting on these inconsistencies to actually improve the curation/tagging of the software in the marketplace.
I hope it helps a bit!
in order to synchronize services from the ssh open marketplace, it is not enough to query for services with keyword "DARIAH Resource", we also need to map these services to countries in our database. since countries are not represented in the sshomp data model, we need to map actor names like "DARIAH-AT" to a country.
we should save the sshomp actor id as a field in our country table (maybe also the name).
also, services should also store the sshomp id/url - we have a
marketplaceUrl
field for software, but not for services.on the sshomp side, we may want to add an explicit DARIAH
identifierService
. and, we should includeaccessibleAt
in search results from/api/item-search
so we can populate the service'surl
field.still think syncing the other way around (pushing services created in unr to sshomp via sshomp api) makes more sense. e.g. how would we populate the "service size" field in unr when ingesting services from sshomp.
also, let's make
marketplaceStatus
a proper enum (probably reflecting the actual status field in sshomp), instead of yes/no.do we have a way to distinguish Tools (Software) and Service in MP? (I believe we have a dedicated type-field)