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

Update content of REGISTRATION_TYPE content #8486

Closed
yuisotozaki opened this issue Aug 5, 2021 · 7 comments
Closed

Update content of REGISTRATION_TYPE content #8486

yuisotozaki opened this issue Aug 5, 2021 · 7 comments
Assignees
Labels
Assets bug Something isn't working Dev Tasks for developers

Comments

@yuisotozaki
Copy link
Collaborator

yuisotozaki commented Aug 5, 2021

This ticket is a follow-up to #7885 where we updated the search result PDF content.

The current system sometimes shows registration type AND act. The new registration_types table's registration_desc and registration_act field values need to be cleaned up so that the description field contains the description and act field contains the act.

When this is completed, we can introduce the Act field to the search result PDF (#7885) and we won't have strange duplicate values showing.

Reference:
Registration descriptions updated 2021-12-07 (use columns J & K to update the Registration_types table)
https://app.zenhub.com/files/157936592/2a97ecdd-55e0-463b-9b45-573c475f51a3/download

@yuisotozaki
Copy link
Collaborator Author

@Kaineatthelab This database field value update will contribute to more informative output in the PDF. See Patrick's input in this comment.

@jinghualicgi
Copy link
Contributor

@chdivyareddy Divya, please verify this

@PatrickAHeath
Copy link
Contributor

PatrickAHeath commented Dec 7, 2021

The registration description for Crown Charges in the Registration_Types table references the Act that the charge is against. The Act column in the table will be 'Miscellaneous Registrations Act', which is what ties Crown Charges to PPR. If both the description and the Act are displayed on search result and verification statement PDF outputs, all information about the registration is provided. For Crown Charge registration type OT - Other - the Act displayed on the PDF is the act that the client entered, not the value from the registration_types table. All other types can use the Registration_Act value from the table.

@jinghualicgi jinghualicgi added the bug Something isn't working label Dec 8, 2021
@PatrickAHeath
Copy link
Contributor

Feedback from Kevin's Testing:

A MRR crown charge registration where the Act name selected is “Other” (i.e. to be entered by the registering party) is displayed:
a. With the registration type labelled “Other” – This should be an indication that it is a crown charge under the MRR.
b. In the verification statement and search result reports, the referenced Act is not displayed.
Between these two, required material information – the name of the Act that gave rise to the interest – is effectively absent from the registration. The Act name should be displayed in the verification statement and all search result reports.

@PatrickAHeath
Copy link
Contributor

Considering Kevin's comments to preserve the 'MISCELLANEOUS REGISTRATIONS ACT' for Registration Type 'Other' and to be consistent with the other Crown Charge registrations for specific acts within the Miscellaneous Registrations Act which have the registration type as 'CROWN CHARGE FILED PURSUANT TO ' followed by the specific Act Name, do the following for Registration Type Other:

  • set the registration name to "CROWN CHARGE - OTHER - FILED PURSUANT TO " followed by the Act Name entered by the client converted to caps.
  • For the Act Name, use the value from the db for registration type 'OT' - "MISCELLANEOUS REGISTRATIONS ACT"

@doug-lovett doug-lovett self-assigned this Jun 10, 2022
@doug-lovett
Copy link
Collaborator

Assuming the value for the OT type act name is the other description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Assets bug Something isn't working Dev Tasks for developers
Projects
None yet
Development

No branches or pull requests

6 participants