✔ Dispute Documents with no PDF available
Completed by Morgan M.
- Assigned to
-
Harsh P.
Irit W.
Paul M.
- Notes
-
Further to
This means that the dispute documents should not be uploaded to the new application:
The remaining 296 dispute documents were marked with "0" under Publicly Available and "1" under Upload to New:
This means the dispute documents should be added to the new application; however, because there is no PDF document available, the Publicly Available field is set to "No" as outlined in the ISLG Data Migration Meta Field Map: https://docs.google.com/spreadsheets/d/1Ho_yBR8gfCIqivmvkPy_hISkDGozdWsXxn46ImeQ-V4/edit#gid=0
This means that the following placeholder message should be displayed in place of the PDF on the subscriber side of the application:
Document is not publicly available.
cc
The following two spreadsheets list the Dispute Document UINs where the PDF document is unavailable.
1) In the UIN Master, Dispute Document tab, there are 296 Dispute Documents marked with "0" under Publicly Available and "1" under Upload to New.
As Morgan mentioned above, the following placeholder message should be displayed in place of the PDF on the subscriber side of the application:
Document is not publicly available.
***
2) In the UIN Master, Dispute Document tab, there are 49 Dispute Documents marked with "0" under Upload to New. These are the Dispute Documents that should not be uploaded to the new application:
Thank you,
Irit
Are we missing a document from the list above? I thought there was 50 documents with "0" under Upload to New? Note there should be a total of 346 documents.
Thanks,
Morgan
We have 49 documents with "0" under Upload to New. The Dispute Document you found earlier (IC/0297/222) was part of that list of missing documents that Harsh sent. It is now uploaded to the Admin Site.
Thanks,
Irit
Thanks,
Morgan
cc
Update. The following two spreadsheets list the 346 Dispute Document entries where a PDF document is unavailable.
1) Placeholder required.
In the UIN Master, Dispute Document tab, there are 327 Dispute Documents marked with "0" under Publicly Available and "1" under Upload to New.
As Morgan mentioned above, the following placeholder message should be displayed in place of the PDF on the subscriber side of the application:
Document is not publicly available.
*****
2) Do not include in the new application.
In the UIN Master, Dispute Document tab, there are 19 Dispute Documents marked with "0" under Upload to New. These are the Dispute Documents that should not be uploaded to the new application:
Thank you,
Irit
Morgan
As per your above comment, Now only 19 documents we need to remove and remaining 327 documnets make publicly not avialble mean only placholder pdf will be availble on those 327 documents.
Am i correct?
Morgan
Following up on the above, could you please confirm whether the changes have been implemented on rebuild.islg.
Thanks,
Morgan
Yes, this change is implemented on rebuild.islg as well.
Thanks,
Morgan
I tested several of the 327 Dispute Documents that were marked with "0" under Publicly Available and "1" under Upload to New in the UIN Master. On the rebuild subscriber site, when I click on the Full Citation, a PDF opens with the following message displayed:
DOCUMENT IS NOT PUBICLY AVAILABLE
Screen capture, rebuild live site:
Or is this PDF with "document not publicly available" message correct?
The 19 Dispute Documents marked with "0" under Upload to New in the UIN Master are not uploaded to the new application as per the instructions given.
Thanks,
Irit
For the document above (IC/0440/01), the setting of the document seem correct with the "Publicly Available" field marked "No", but I can't find any requirements on TargetProcess that confirm what is supposed to happen on the Subscriber side of the application when this field is set to "No".
Thanks,
Morgan
Just following up on above, could you just direct me to the user story that outlines the subscriber side requirements for the "Publicly Available" field set to "No", and I'll determine whether we have an issue.
Thanks,
Morgan
I don't believe we ever created criteria for what should happen with the "Publicly Available" toggle. I can't find criteria related to this in TargetProcess nor remember having discussions with DevIT about this either. As this isn't a hardcoded field as well, this leads me to believe we never determined specific behaviour for it.
Thanks,
Morgan