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

Change text "expired" on Relationships section of entity page #151

Closed
swcurran opened this issue Feb 14, 2022 · 4 comments
Closed

Change text "expired" on Relationships section of entity page #151

swcurran opened this issue Feb 14, 2022 · 4 comments
Assignees

Comments

@swcurran
Copy link
Contributor

I noticed that the "expired" appears in the "Relationships" tab. See: https://orgbook.gov.bc.ca/entity/BC0338518

In that case, it is the organization that has been dissolved - not the credential. As such, the text should say "Historical", not expired, and the date should be the effective date of the dissolution -- e.g. for https://orgbook.gov.bc.ca/entity/FM0562397 it should be Oct 01, 2019.

See if this is an obvious change. If not, we can discuss the related data in a meeting with @ianco and the BC Registries folks.

@WadeBarnes WadeBarnes transferred this issue from bcgov/orgbook-configurations Feb 15, 2022
@wadeking98
Copy link
Contributor

wadeking98 commented Feb 17, 2022

The text is straightforward, but the date doesn't seem to be an obvious change. Right now there's no way to grab the dissolution date from a relationship credential, because the dissolution date exists on a different credential. We will have to meet to discuss a work around.

@swcurran
Copy link
Contributor Author

If the "expired" refers to the credential, then it should be prefixed with "Credential" to make it clear.

Would that solve your problem?

@wadeking98
Copy link
Contributor

Yes that would work

@wadeking98
Copy link
Contributor

closed by PR: #159

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants