| Issue Number | 4993 |
|---|---|
| Summary | Global change to remove Exclude From Glossifier = Yes |
| Created | 2021-06-17 10:28:27 |
| Issue Type | Task |
| Submitted By | Osei-Poku, William (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2021-06-24 16:19:12 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.292362 |
Since we can now glossify alternate name glossary terms (
OCECDR-4960) We would like to
i. identify all glossary terms that have Name Type = Alternate, and have
been
ii. marked as ExcludeFromGlossifier = Yes
Could you please run a custom global change to remove ExcludeFromGlossifier = Yes from these alternate name terms so that they can be picked up by the glossifier ?
I realize this might sound picky, but if we look for "Alternate" (instead of "alternate") the global change job won't do anything. 😉
Global change run on DEV in test mode.
I am getting a permissions error:
Traceback (most recent call last): File "D:\inetpub\wwwroot\cgi-bin\cdr\ShowGlobalChangeTestResults.py", line 549, in <module> Control().run() File "D:\inetpub\wwwroot\cgi-bin\cdr\ShowGlobalChangeTestResults.py", line 53, in run elif self.text: File "D:\inetpub\wwwroot\cgi-bin\cdr\ShowGlobalChangeTestResults.py", line 177, in text with open(path, encoding="utf-8") as fp: PermissionError: [Errno 13] Permission denied: 'D:/cdr/GlobalChange/2021-06-24_16-03-10/CDR0000792692.cwd.diff'
D:\cdr\Log\tmplrse8tkc.html contains the description of this error.
I remember how adamant CBIIT was when they insisted this problem never happens on their servers. 😛
Please try again.
I am able to access it now. Thanks!
It looks like the access issue has resurfaced.
Traceback (most recent call last): File "D:\inetpub\wwwroot\cgi-bin\cdr\ShowGlobalChangeTestResults.py", line 549, in <module> Control().run() File "D:\inetpub\wwwroot\cgi-bin\cdr\ShowGlobalChangeTestResults.py", line 56, in run self.show_report() File "D:\inetpub\wwwroot\cgi-bin\cdr\ShowGlobalChangeTestResults.py", line 70, in show_report page = self.report.page File "d:\cdr\lib\Python\cdrcgi.py", line 750, in report tables = self.build_tables() File "D:\inetpub\wwwroot\cgi-bin\cdr\ShowGlobalChangeTestResults.py", line 28, in build_tables opts = dict(columns=self.columns, caption=self.caption, id="docs") File "D:\inetpub\wwwroot\cgi-bin\cdr\ShowGlobalChangeTestResults.py", line 94, in caption f"Total number of documents = {self.docs.count}", File "D:\inetpub\wwwroot\cgi-bin\cdr\ShowGlobalChangeTestResults.py", line 211, in count return len(self.docs) File "D:\inetpub\wwwroot\cgi-bin\cdr\ShowGlobalChangeTestResults.py", line 226, in docs self._docs = [self.Doc(self, cdr_id) for cdr_id in self.files] File "D:\inetpub\wwwroot\cgi-bin\cdr\ShowGlobalChangeTestResults.py", line 235, in files for filename in listdir(self.directory): File "D:\inetpub\wwwroot\cgi-bin\cdr\ShowGlobalChangeTestResults.py", line 218, in directory self._directory = f"{self.control.base}/{self.control.directory}" File "D:\inetpub\wwwroot\cgi-bin\cdr\ShowGlobalChangeTestResults.py", line 85, in base self._base = f"{self.session.tier.basedir}/GlobalChange" File "d:\cdr\lib\Python\cdrcgi.py", line 819, in session self._session = Session(session) File "d:\cdr\lib\Python\cdrapi\users.py", line 85, in init raise Exception("Invalid or expired session: {!r}".format(name)) Exception: Invalid or expired session: '60D4E52C-3774CD-002-58L7SS8KGX6B'
D:\cdr\Log\tmp_p2orwh7.html contains the description of this error.
That's a different problem. I had given you a URL which used my own current session. I should have given you a sessionless URL.
https://cdr-dev.cancer.gov/cgi-bin/cdr/ShowGlobalChangeTestResults.py?dir=2021-06-24_16-03-10
Thanks! Looks good. Please run in live mode on DEV.
Live mode on DEV has completed successfully.
Verified on DEV. Please run in test mode on QA. Thanks!
Done. https://cdr-qa.cancer.gov/cgi-bin/cdr/ShowGlobalChangeTestResults.py?dir=2021-07-09_08-57-30
Verified. Please run in live mode on QA. Thanks!
Done.
Please run in test mode on PROD. Thanks!
The URL points to DEV. Is the data from PROD?
Yes. We aren't allowed to log into the production server (or stage, for that matter) with RDP, so we have to run the global change elsewhere, which means the logs get written elsewhere. But the job runs with the documents from the tier we identify, which in this case was PROD. That's the way it always happens when we run a test global change for PROD.
OK. Got it. Thanks!
Please proceed to run in live mode on PROD.
Has this global completed ?
Yes. Looks like Jira discarded my previous comment.
OK. Thanks! I will review and close the ticket.
Verified on PROD. Thanks!
Elapsed: 0:00:00.001366