The links in the application's footer all link back to the search page rather than the expected content.

Example site: https://frontend-v2-test.apps.silver.devops.gov.bc.ca/

They should link to the same content as they do in the existing version of the OrgBook; https://orgbook.gov.bc.ca/en/home

Disclaimer: https://www2.gov.bc.ca/gov/content/home/disclaimer
Privacy: https://www2.gov.bc.ca/gov/content/home/privacy
Accessibility: https://www2.gov.bc.ca/gov/content/home/accessible-government
Copyright: https://www2.gov.bc.ca/gov/content/home/copyright

In the Old OrgBook UI, the advanced search feature has commonly used in demos to find a company with a specific type of credential. This is probably the only use of the "advanced search". Not particularly useful, but great for demos when you don't know the names of companies that have a specific type of credential. We (and especially @watkinspd and @jljordan42 ) would like that "Show me a list of companies with a given credential".

One idea for doing that, might be on this screen (image below), where we show all the credential types. Could the credential types be a link or perhaps have a "magnifying glass" search icon beside them that when clicked went to the search screen showing a list of that credential type.

Open to other ideas of how to get this feature back. Will it screw up the new search screen (because its using a different API or search parameters), or can we get to the search screen in that context?

For now, go with:

Relationships in OrgBook BC indicate that two registered entity have some sort of formal connection defined in BC Registries. The most common is the “Doing Business As” or “DBA” relationship, where one registered entity is just a name by which another registered entity does business. In OrgBook BC, both entities will have a relationship credential that indicates their side of the relationship that references the other. For example the DBA entity would indicate “Is owned by” and reference the owning entity, while the owning entity would indicate “Doing business as” and reference the DBA entity.

Resolved: Do we know the full list of relationships? If so, I might add more to this text to define other pairs of relationships.

We also need tooltips for the other items in the image below. @alexgmetcalf -- could you please you add some tooltip text for each of the items to this ticket?

Hello, could the following be added into ORG book TST environment, please let me know if you need any more information.
Thank you!

1. PACIFIC GOLD COAST NURSERIES - BN: 99467 3507 BC0001 - Registration# FM1006227
2. A5 Parks – General Partnership (legal name Jane C Finley, Maurice T Hood) Registration# FM1006229
3. VICTORIA REPAIR PATROL CORP. (incorporation # BC0913275)
4. Jourrapide Societies Association (Society) NR 9948698 (BN: 994650703 BC0001)
5. FIXENT CARRIERS CORP. (BC0919040)
6. JUPITER COURIERS LTD.(BC0919041)
7. Groot Trucking Corp (BC0919042)

Provide more details on how to develop the application.

Assuming this is not too difficult, here is what I suggest for the up and down arrows.

• Up -- just record the action such that we can see it in the analytics.
• Down -- record the action so that we can see it in the analytics, and popup:

"Sorry you didn't have a great experience. Would you like to contact us and submit a suggestion or question about the service?"

Include a "Yes" / "No" (or whatever you think...) and if they say yes, send them to the contact us page.

If possible, do NOT show the "How was your experience" button on the Contact page.

Example record: https://orgbook.gov.bc.ca/entity/BC0928747

Steps to reproduce:

• Navigate to the example record, or any other record with relationships.
• Click on any of the relationships to view the related organization's details.
• Scroll to the relationships section of the screen.
• Open the Credential status for a related organization.
• Hover over the Credential verified link.

Observed behavior:

• The link is https://orgbook.gov.bc.ca/
  

Expected behavior:

• The link to be the url of the organization's credential details page. https://orgbook.gov.bc.ca/entity/BC0928747/credential/1485679 in the case of this example.

In the current environment for the new UX, the translations for the credential types for Registries (registration, business_number and relationship) are missing. Please add them.

See: https://frontend-v2-dev.apps.silver.devops.gov.bc.ca/search?q=inc&category%3Aentity_type=&credential_type_id=&inactive=&page=1

Fix up the manage script so a ./manage build ./manage start will work for a clean checkout

Currently the vue.js.config file needs to be edited for a local build/run

From the list of things left to do, this item is:

The dialog boxes have been implemented, but we need the content for the entity page dialog boxes. The wireframe does not provide any usable content for dialog boxes. We need to dicuss what content to place in the entity dialog boxes

Please provide a sample or link to an example of this. I'm not clear what is needed and where.

Example: https://frontend-v2-prod.apps.silver.devops.gov.bc.ca/entity/BC0928747

Locate a credential in the list and click on the Credential verified link to view the credential:

Now click the link to go back to the company detail screen. You end up at the top of the page and the credential you had opened is now closed, so you have completely lost your place on the page.

I find the current ("make it like Amazon") filters difficult to understand.

Here is what I would suggest:

• the numbers should remain with the full list counts after an update due to filtering.
• the "See more" should only list an entity if it has a non-zero count. If there are none, I would leave the "See more" off.
• once an item is picked in a category, add a "Clear" in that category on the left side menu.

Happy to discuss these further and what complexities these introduce.

Please integrate GDX analytics into the new UI.

References:

• bcgov/orgbook-bc-client-angular#18
• bcgov/orgbook-bc-client-angular#20
• https://github.com/bcgov/orgbook-bc-client-angular/blob/f37d06baac316d5732683cc3096cac79b70017f8/src/index.html#L26-L53

A user reported that the link to the API demo is broken. Please find the link and remove from OrgBook.

Once you click on one of the thumbs in the "How was your experience?" section of the page there is no way to cancel it without refreshing the page. The display persists from page to page until you refresh.

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

The current order is Organization Type, Organization Status, Credential.

I'd recommend putting Organization Status at the top of the list. The first thing I find myself doing all the time is filtering by Active status to remove all of the noise of the Historical companies.

Or perhaps put the Organization Status options at the top of the list and enable the Active option by default. Unlike the previous UI this one lists the filter options at the top of the results, making it more obvious which filter options are being used.

Examples:

• https://orgbook.gov.bc.ca/entity/BC0928747
• https://orgbook.gov.bc.ca/entity/FM0414526

In the credential timeline of the example records the registration number listed for each of the related organizations is the registration number of the organization being viewed (see screenshots below).

Should the registration numbers be for the listed (related) organization itself and not that of the organization being viewed.

All registration numbers are listed as BC0928747:

All registration numbers are listed as FM0414526:

Comparing the filtering logic between search and the credential timeline as we are looking to change the way filtering is done for search results (i.e. to remove drilling-down of results). I noticed some odd results when filtering credentials on the timeline.

Take, for example the following results:

Assuming the following filter is applied first:

When I subsequently apply a filter for credential type:

It appears the filters are being ANDed when they should be ORed based on previous suggestions as to how filtering should operate. Each successive application of filters should expand the results, with the default being to show all results when no filters are applied.

This may require some further discussion from @swcurran and @wadeking98

The terms of service link on this page, https://frontend-v2-test.apps.silver.devops.gov.bc.ca/about/orgbook-api, links to The Apache License info here; https://github.com/bcgov/orgbook-api/blob/main/LICENSE.

It should link to an actual terms if service page, which describe the terms of service for the API.

Example: https://frontend-v2-prod.apps.silver.devops.gov.bc.ca/entity/BC0928747

Right click on the Credential verified links and select open link in new tab.

The new tab opens to the OrgBook home page:

Rather than the expected credential detail page:

Several of the Organization Types are sharing the same pop up description for BC Corporation. For example Extraprovincial Company, BC Community Contribution Company, Private Act, Foreign Registration, and others.

Where others like Cooperative and General partnership have their own description:

Each Organization Type should have it's own pop up description.

The new UI advertises you can search by permit number. This is not working.

Using the permit number from here; https://test.orgbook.gov.bc.ca/en/organization/registration.registries.ca/BC0091892/cred/3580366

The new UI turns up zero results; https://frontend-v2-test.apps.silver.devops.gov.bc.ca/search?q=M-238&category%3Aentity_type=&credential_type_id=&inactive=&page=1

We've had feedback that searchers have had trouble with some searches, especially when punctuation is involved. We want to provide some guidance for those searching on the home page near the "Find an organization" autocomplete widget and on the search results page near the "XXX result(s)" indicator. Basically, we need two buttons/icons/links and for each a popup with text that I can provide.

The issues I'm trying to address are these, from the "dislike" comments we've received:

• I searched for "BKV Social Enterprise Co." and I received 1295 results. This does not help me to find the BC Registry ID because I neither have the time nor inclination to search through that many results. The previous version of OrgBook would have returned the result (FM0824270) I was searching for. Return only results for the exact search entered NOT all Business names that contain similar words. (this is an example of the punctuation problem -- had they just searched "BKV", they would have had only 3 results

• advanced search - i can't sift through 1500+ results. ability to refine searches though the search terms, not just the categories (likely same as above)

• when the organization name contains punctuation, the searching is bad. On the main page we need to help them with that.

• at times many, many results come up and we want to provide them guidance that we have about that.

I'd like @alexgmetcalf to weigh in on the UI element -- the buttons/icons/links to be used. Alex -- please mock up some images for what to use in the two places.

Here is a first cut of the text to use in both places. Alex/others -- feel free to improve on this. Worst case, we start with this and we can evolve it as needed:

Help Text

The OrgBook searching by legal name returns all of the organizations that have any of the words that you search on, and floats the most likely matches to the top of the list. In most cases, that means that putting the fully legal name of the entity will float that result to the top. However, in some cases you may find that you get both many (many!) search results, and the entity you are looking for is not at the top. This most often happens when the legal name has punctuation marks -- for example a period "." at the end of the name, e.g. "Co." or "Inc.". It's a problem with the search tool we are using -- we're working on a fix!

When you get too many results and the name you are looking for is not at the top, we recommend that you put only the least common word (or two) from the name. For example, when searching for "BKV SOCIAL ENTERPRISE CO.", about 1300 results are returned, with the top ones having "Social" in them. That darn trailing period! In this case "BKV" is the least common word, so let's only search for that by typing "BKV" into the search bar and hitting ENTER (e.g. don't pick anything from the drop down list). The result is now just a couple of entries, one of which is the one we want.

Remember as well that with OrgBook, you don't have to search on the legal name. You can also search on the BC Registries ID (has two characters and 7 digits, like FM1234567) and by the CRA Business Number (9-digits) for the entity. If you know one or both of those values, using those for an existing entity will always find an exact match.

If you still can't find the entity you are looking for (and you are pretty sure it exists), please use the "Contact" link at the top of the page to let us know what you are looking for and that you can't find it, and we'll see if we can help.

Vuetify's combobox component is being used for the search bar with autocomplete. Voice Control on iOS cannot properly focus the input when prompted. The same issue can be observed with Vuetify's autocomplete component but not with its regular text and select inputs.

I propose we rewrite the search bar using strictly a text input and attach logic for an autocomplete list.

v2 results look like this:

v1 results look like this:

Yet the search results remain the same:

Is this expected behavior?

We are currently using the default Vue icons, but should be using BC Gov ones.

@CharlesMacpherson -- same as previous. Should be with Dwayne to resolve, but I don't know his GitHub handle. Please help if you know how or pass this issue to Some One Else.

Thanks

A good enhancement would be to add the ability to 'clear' search results and the query from the search bar. This becomes especially useful in mobile views.

TL;DR 🏎️

Teams are encouraged to favour modern inclusive phrasing both in their communication as well as in any source checked into their repositories. You'll find a table at the end of this text with preferred phrasing to socialize with your team.

Words Matter

We're aligning our development community to favour inclusive phrasing for common technical expressions. There is a table below that outlines the phrases that are being retired along with the preferred alternatives.

During your team scrum, technical meetings, documentation, the code you write, etc. use the inclusive phrasing from the table below. That's it - it really is that easy.

For the curious mind, the Public Service Agency (PSA) has published a guide describing how Words Matter in our daily communication. Its an insightful read and a good reminder to be curious and open minded.

What about the master branch?

The word "master" is not inherently bad or non-inclusive. For example people get a masters degree; become a master of their craft; or master a skill. It's generally when the word "master" is used along side the word "slave" that it becomes non-inclusive.

Some teams choose to use the word main for the default branch of a repo as opposed to the more commonly used master branch. While it's not required or recommended, your team is empowered to do what works for them. If you do rename the master branch consider using main so that we have consistency among the repos within our organization.

Preferred Phrasing

Pro Tip 🤓

This list is not comprehensive. If you're aware of other outdated nomenclature please create an issue (PR preferred) with your suggestion.

On this page: https://frontend-v2-prod.apps.silver.devops.gov.bc.ca/about/orgbook-data

The BC Registries credential types are not being translated (see image). Please fix this and see if we can make sure this is not a problem elsewhere? It's odd that the non-Registries ones are working on this same screen.

Example: https://frontend-v2-test.apps.silver.devops.gov.bc.ca/entity/FM0389260

On the company results page, the left hand column has inconsistent use of information pop ups:

The titles Credentials, Authority and Registration type all have info pop ups, but Credential type, Date effective, and Show Expired do not. Show Expired is somewhat self explanatory, however the others could use info pop up for consistency.

Example: https://frontend-v2-test.apps.silver.devops.gov.bc.ca/entity/PA0000357

Example record: https://frontend-v2-prod.apps.silver.devops.gov.bc.ca/entity/BC0928747

Steps to reproduce:

• View the relationships for the example record.
• Set the number of Items displayed to 100.
• Now change the number of Items displayed to a smaller number.

Observed behavior:

The page starts out looking like this:

The page ends up looking like this:

Similarly if you change from a smaller number to a larger number you end up with this:

Before:

After:

Expected behavior:
The display to re-focus to the top of the Relationships like this, whenever the Items displayed is changed:

Example Record: https://orgbook.gov.bc.ca/entity/CP1002773

Referenced from #20 #20 (review)

Please try, where possible, as needed, to incorporate some of the features from the nginx configurations into the new Caddy configuration; nginx.conf.template, and run script.
Specifically:

• Configurable rate limiting.
• Proxies for notification web hooks, and static content; https://github.com/bcgov/orgbook-bc-client/blob/main/docker/nginx-runtime/s2i/bin/run#L30-L65
• Addition of common security headres; https://github.com/bcgov/orgbook-bc-client/blob/main/docker/nginx-runtime/nginx.conf.template#L72-L77
• Additional forward headers if needed; https://github.com/bcgov/orgbook-bc-client/blob/main/docker/nginx-runtime/s2i/bin/run#L17-L26
• Deny list support

The content for the translations of the Registration Event Types can be found here:

https://docs.google.com/spreadsheets/d/1gfn6UACE88vcPYCEI96GVHPLdGxMcKGvZp6ZM33s0kg/edit?usp=sharing

Please review and determine how best to get this added to the BC OrgBook Client Vue.

We need content for the following OrgBook BC buttons in the footer:

• Disclaimer
• Privacy
• Accessibility
• Copyright

I assume that there is standard BC Government content that should go there.

Should OrgBook BC use a "standard BC Gov" footer and not have our own content on those page? Is that technically possible?

@CharlesMacpherson -- assigning this to you for now, but it should be with Dwayne Gordon. I just don't know his GitHub handle. On the other hand, you might know GDX procedures for this. Feel free to reassign this (ideally to Dwayne) if you don't know what to do with this.

In the Relationships section of the company details screen the next and previous page buttons always enabled, even when there are no other pages to display.

Example records:

• https://frontend-v2-prod.apps.silver.devops.gov.bc.ca/entity/BC0722797
• https://frontend-v2-prod.apps.silver.devops.gov.bc.ca/entity/BC0928747

Similarly the previous button is enabled even when on the first page of a multi-page display:

and the next button is enabled even when on the last page of a multi-page display:

TL;DR

Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).

Why Topic

In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means it's critical that we work to make our content as discoverable as possible. Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.

What to do

Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic.

That's it, you're done!!!

How to use

Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.

Pro Tip 🤓

• If your org is not in the list below, or the table contains errors, please create an issue here.

• While you're doing this, add additional topics that would help someone searching for "something". These can be the language used javascript or R; something like opendata or data for data only repos; or any other key words that are useful.

• Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.

• If your application is live, add the production URL.

Ministry Short Codes

NOTE See an error or omission? Please create an issue here to get it remedied.

Reported by @DJ-Gordon.

When possible can somebody take a look at the line breaking for the links on the main page. It does not look great on Mobile when “OrgBook” break.

Example record; https://frontend-v2-prod.apps.silver.devops.gov.bc.ca/entity/BC0928747

ctrl-click a relationship link. The link to the related record opens as expected in a new tab, however the operation also drops open the credential status for the record:

Right-click, open link in new tab does not do this. It leaves the credential status collapsed and opens the link in a new tab as expected.

I think it is time...

The term "In Good Standing" has legal ramifications that we can't imply on the site, and the data we are using to display the data is not sufficient. Please change the display to say "Active" and "Historical" instead of "In Good Standing" and whatever other term we are using.

If we are using "Archived" let me know and we can discuss. We need to be consistent in using the same term across the site when we mean "A dissolved organization" -- and a different term then when we are talking about a "credential that is no longer active".

This has to be done before launch. Sorry for the late notice.

Observed: https://frontend-v2-prod.apps.silver.devops.gov.bc.ca/about/orgbook-data

Expected: https://frontend-v2-test.apps.silver.devops.gov.bc.ca/about/orgbook-data

• Minus the duplicate BC Mines Act Permit

Please use the following text:

Not finding your organization in OrgBook BC?

One reason you might not be finding the entity for which you are searching is that the organization has not been registered with BC Registries. If the organization has been registered, search for the BC Registries ID (it has a format like "FM1234567"). You can also try searching by your 9-digit Business Number from CRA, if that number is registered with BC Registries.

If you need to register the organization, these links may help. Register your business in BC or follow the full step-by-step guide to starting a BC business.

If you need additional information, please contact the BC Registries Help Desk via email [email protected], or by calling the BC Registries Help Desk at 1-800-663-6102.

Example record: https://frontend-v2-prod.apps.silver.devops.gov.bc.ca/entity/BC0928747

Click on a relationship record to view it.

To navigate back to the original record you have to click the browser's back button or use an equivalent method (shortcut, back button on a mouse, etc.), as the page itself does not provide a link back to the previous record, only to the main search screen.

We recently received a "dislike" with a valid comment that I would have liked to respond to, but there was no email address available. As well, it would be nice for users to be able to just Like/Dislike without getting a "make a comment" box that they have to cancel. I recommend the flow be:

1. Offer the "Like/Dislike" as today.
2. On click, record a record of the click -- like/dislike and date/time.
3. Change the Like/Dislike to "Submit a comment/suggestion" and have that as the footer for the remainder of the session. This would prevent submitting multiple like/dislikes in a session.
4. If they click to submit a comment/suggestion, take them to the "normal" request page that includes the being able to make a comment/suggestion with an email address so we can respond.

We also need to document how we can see the like/dislike history. Perhaps a secret URL that we can bookmark that shows a summary (all time, last year, last 30 days, last 7 days) with counts?

The relationship records on the company details screen do not link to the corresponding company record as expected, rather they just open a drop down to display a little more info.

Example: https://frontend-v2-prod.apps.silver.devops.gov.bc.ca/entity/BC0722797

I would expect the link to open to this record:

Instead it does this: