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

Issue 433: Fix some resource searches #434

Merged
merged 2 commits into from
Jun 19, 2018

Conversation

veggiematts
Copy link
Contributor

Fix for issue #433

This patch fixes the following resource searches:
Funds
Note type
Note content
Purchase site
Authorized site
Administering site
Authentication type
Cataloging status
Workflow step

This patch fixes the following resource searches:
Funds
Note type
Note content
Purchase site
Authorized site
Administering site
Authentication type
Cataloging status
Workflow step
@veggiematts veggiematts added the bug This is a bug (not an enhancement) label May 28, 2018
@xsong9 xsong9 added this to the Version 3.0.0 RC milestone Jun 5, 2018
@queryluke
Copy link
Contributor

@cjc66 Asked me to test this. Before it seems the searches were returning 500 errors. While they no longer return 500 errors, some of the searches do not appear to work as intended.

Authorized Site, Administering Site
Though I have an authorized and administering site set in the acquisitions tab, filtering on those values returns 0 results.
screen shot 2018-06-18 at 9 18 31 am

Note Type & Content: Notes on the product tab are not search
Though I have a Product Details note, filtering by Note Type "Product Details" returns 0 results.
screen shot 2018-06-18 at 9 25 52 am

However, if I filter by Note Type "Access Details", I get results because this second note exists in the acquisitions tab. The same is true for access & cataloging tabs.
screen shot 2018-06-18 at 9 30 31 am

LEFT JOIN ResourceAuthorizedSiteLink RAUSL ON R.resourceID = RAUSL.resourceAcquisitionID
LEFT JOIN ResourceAdministeringSiteLink RADSL ON R.resourceID = RADSL.resourceAcquisitionID
LEFT JOIN ResourcePayment RPAY ON RA.resourceAcquisitionID = RPAY.resourceAcquisitionID
LEFT JOIN ResourceNote RN ON RA.resourceAcquisitionID = RN.entityID
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One problem is that the ResourceNote table "entityID" field only exists in the 3.0.0/002-350.sql upgrade script, so it (and maybe more) needs to be added to the main install.sql (right? is that still our approach to fresh installations?).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure. I thought we decided that fresh installs would process install.sql and the upgrade scripts. Can someone confirm this?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@veggiematts, correct. When installing the scripts process install.sql and all upgrade sql files as long as the upgrade files are contained within a version directory, e.g. /$MODULE/install/protected/$VERSION

Here is the PR

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@queryluke @veggiematts Got it. Thanks for the clarification.

@veggiematts
Copy link
Contributor Author

This follow-up should fix the problems @queryluke mentioned.

@queryluke
Copy link
Contributor

Yes, I have confirmed this is working.

@veggiematts veggiematts merged commit f90f9c7 into coral-erm:development Jun 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This is a bug (not an enhancement)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants