You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We still see a couple of outdated credential items listed under Data Types, can we update this page to reflect active credentials only?
Ministry of Energy, Mines and Low-carbon Innovation - BC Mines Act Permit (we have a new credential in development)
Ministry of Environment and Climate Change Strategy - Annual GHG Emissions Report
Stephen's comments via email: "I'm not sure how the page is generated - probably based on what issuers are configured. Perhaps the best fix, if that is the case, is to change the condition for being listed to "Configured AND Has more than 1 credential in OrgBook". The latter condition would eliminate those two from showing"
The text was updated successfully, but these errors were encountered:
Correct. This list is constructed based on the registered issuers (and the credential types they've indicated they issue), whether or not any credentials have been issues by those issuers. For example, apart from those you've identified, there is the BC Registries Address Credential. Though BC Registries is an active issuer and has registered a schema for an Address Credential, no Address Credentials have ever been issued.
We still see a couple of outdated credential items listed under Data Types, can we update this page to reflect active credentials only?
Ministry of Energy, Mines and Low-carbon Innovation - BC Mines Act Permit (we have a new credential in development)
Ministry of Environment and Climate Change Strategy - Annual GHG Emissions Report
Stephen's comments via email: "I'm not sure how the page is generated - probably based on what issuers are configured. Perhaps the best fix, if that is the case, is to change the condition for being listed to "Configured AND Has more than 1 credential in OrgBook". The latter condition would eliminate those two from showing"
The text was updated successfully, but these errors were encountered: