Issue Number | 5019 |
---|---|
Summary | Modify Licensee Schema |
Created | 2021-08-13 11:23:59 |
Issue Type | Improvement |
Submitted By | Englisch, Volker (NIH/NCI) [C] |
Assigned To | Englisch, Volker (NIH/NCI) [C] |
Status | Closed |
Resolved | 2022-06-13 21:39:49 |
Resolution | Fixed |
Path | /home/bkline/backups/jira/ocecdr/issue.296509 |
We had discussed to enhance the information we're capturing for our PDQ partners like
allowing multiple user accounts
using different status values for active, active in name only (a.k.a "idle"), test, etc
other TBD
We will need to do the research to identify software which assumes that there is only one login account and modify the code to support one-to-many relationships.
The following scripts and ad-hoc queries seem to be affected by a Licensee Schema (multiple user ID) change:
licensee_list.py
Monthly scheduled report producing report named "List of PDQ Content
Distribution Partners"
get-pdq-contacts.py
Identify active PDQ Partners
get-pdq-partners.py
Identify partners used for SFTP retrieval activity
data_parners.py (may not need program changes)
Job to send weekly notification to PDQ Partners
pdq_access_log.py
Used to create monthly download activity
Ad-hoc Query reports
Licensee Accounts
Licensee Accounts (active)
Licensee List
The following changes have been implemented to the schema:
Adding a new element "SecondaryUserName"
Adding a new element "ExternalGmailAddress"
Adding a new element "ContentTranslation"
LOV to be decided; currently: Arabic, Chinese, German, Japanese,
Spanish
Modifying LOV for LicenseeStatus
Adding: Production-idle
Current values: Production, Production-inactive, Test,
Test-inactive
Adding new value for LicenseeType:
Adding: Storefront
Removing: Internal, Printing
Current values: Regular, Special, Internal, Printing
Adding new element UsageDescription
Adding new element InterestedDocTypes
LOV: DrugInformationSummary, GlossaryTerm, Media, Summary, Terminology,
Other (Media-Images, Media-Audio?)
I'm moving this ticket to Ohm since it is part of a group of tickets (schema, CSS, template change).
There were a couple of changes requested after our latest partner meeting:
We would like to identify if our summaries are displayed as-is or modified and if Spanish summaries are displayed from us or translated from our English content.
We still hadn't settled on our partner status values
For #1, I've added a new field called DisplayOfSummaries with the following possible values:
Englisch-(unchanged or modified or fragments)
Spanish-(unchanged or modified or fragments)
For #2, I've added the following values:
Production
Production-inactive
Production-terminated
Test
Test-expired
Test-inactive
NA-Storefront
Our current status of "Test-inactive" will be converted to "Test-expired". Once that is done using a global change we can remove the status "Test-inactive".
The status "Production-inactive" will be converted to "Production-terminated". The status "Production-inactive" will then be used for those partners we're currently identifying as "idle".
The following schema file has been updated on DEV:
Licensee.xml
https://github.com/NCIOCPL/cdr-server/commit/373e5e7
Elapsed: 0:00:00.001283