TicketTopicStatusShort DescriptionText
6557611 Cornell Metadb: request to run automated process to update a table with ERM dataopenrequest to set up a process where hosting team obtains our quarterly EBSCO Consolidated Platform reports in CSV format and run a script we have to append the data to a table in the Cornell Metadb reporting database. The reports are the Title Usage Details reports. The contact for this file is Ashley Murry at EBSCO.

This is the platform for the files: : https://eadmin.ebscohost.com/

Hi Whitney,

One question for the hosting team is whether they can automate running Python scripts on files to load into our Metadb reporting database. Since they have automated a data anonymization process for us, it seems they'd be able to automate running a script on a file to upload to the database and append data to an existing table for us.


All the best,

Sharon Markus

---

4/24/26

Whitney,

Thank you for the update. I have a few more details. For this process, we are asking our hosting team to take the monthly EBSCO eusage data file and append it to an existing table in our Metadb reporting database hosted by EBSCO. We plan to provide the hosting team with scripts to prep the Excel file then upload and append it to a base table in the local_eusage schema.

All the best,

Sharon Markus

----

Hi Sara,

I am following up about the request we have made for you to set up a process where you obtain our EBSCO Consolidated Platform reports in CSV format and run a script we have to append the data to a table in the Cornell Metadb reporting database. We originally mentioned that we would like this process to run quarterly, but now we want it to run monthly.

  • You asked about the similar process we have set up to run on a weekly basis. For this process, an update script is run to anonymize loan data in our tables in our Metadb reporting database.
  • We are not hosting and managing our own Metadb instance. EBSCO is. I do not know where the EBSCO hosting team stores the process. You can contact Sobha Duvvuri or Carole Godfrey for more information about our hosting team.
  • I would expect the script to be executed in our hosted Metadb reporting database environment

For this setup, we are asking EBSCO to retrieve our monthly Title Usage Details reports (an Excel file), run a Python script (supplied by Cornell) to clean the data in the Excel file, and to run an SQL script (supplied by Cornell) to append the cleaned data to an existing table of eusage data in the local_eusage schema in our Metadb reporting database. We would like this done on a monthly basis.

The contact for this monthly file is Ashley Murry at EBSCO.

This is the platform for the files: : https://eadmin.ebscohost.com/

Please let us know if you can work with EBSCO employees Ashley Murray and Sobha Duvvuri to set up this automated monthly process for us.

All the best,

Sharon


----

Hi Sharon,

I wanted to follow up on my previous email.

This response was sent from EBSCO's case management system, so when replying, please use the "Reply" button and respond directly to this email to ensure your response is received and documented in this case.

Thank You,

Sara Lewis

Technical Support Representative II


From: Sara Lewis <auto-response@ebsco.com>
Sent: 3/30/2026 9:00 am GMT-04:00
To: Sharon Markus (slm5@cornell.edu)
Subject: RE: Cornell Metadb: request to run automated process to update a table with ERM data

Hi Sharon,

I wanted to follow up on my previous email.

This response was sent from EBSCO's case management system, so when replying, please use the "Reply" button and respond directly to this email to ensure your response is received and documented in this case.

Thank You,

Sara Lewis

Technical Support Representative II


From: Sara Lewis <auto-response@ebsco.com>
Sent: 3/25/2026 3:41 pm GMT-04:00
To: Sharon Markus (slm5@cornell.edu)
Subject: RE: Cornell Metadb: request to run automated process to update a table with ERM data

Hi Sharon,

Thank you for contacting EBSCO Technical Support.

We are currently reviewing the details and would appreciate a bit more information to understand better how this might be implemented. Specifically:

  • You mentioned that a similar automated process is already running on a weekly basis. Could you share how and where that process is set up?
  • Do you know if your team is hosting and managing your own MetaDB instance?
  • Additionally, could you clarify where you would expect the quarterly script to be executed?

From our initial review, this request appears to be related to processes outside of FOLIO itself and may involve configurations within your MetaDB environment.

Understanding your current setup will help us determine the best way to guide you.

This response was sent from EBSCO's case management system, so when replying, please use the "Reply" button and respond directly to this email to ensure your response is received and documented in this case.

Thank You,

Sara Lewis

Technical Support Representative II


From: Sharon Markus <slm5@cornell.edu>
Sent: 3/24/2026 1:55 pm GMT-04:00
To: Web Service (crmwebsvc@epnet.com)
Subject: Cornell Metadb: request to run automated process to update a table with ERM data

Hosting Team,
We are wondering if you can set up a process where you obtain our quarterly EBSCO Consolidated Platform reports in CSV format and run a script we have to append the data to a table in the Cornell Metadb reporting database. The reports are the Title Usage Details reports. The contact for this file is Ashley Murry at EBSCO.

This is the platform for the files: : https://eadmin.ebscohost.com/

We have another automated process running weekly, and so we are hoping this is manageable on a quarterly basis.

All the best,
Sharon Markus


6579786 Cornell Metadb: please update user access to local_eusage schemacompletegrant Tom Trutt read-write access to local_eusage schema
6557469Cornell Metadb: please create new "local_erm" schemacompletecreated and name was changed to local_eusage schema
6563751 Cornell Metadb: indexing questioncompleteowners of tables in Postgresql can index them

Text of 6563751


Thank you for contacting EBSCO.

Your EBSCO Customer Support Case Number and Title are: 6563751 - "SI 4758546 | Cornell Metadb: indexing question".
_________________________________________________________________

Hello Sharon,

I have received the following update from the hosting team:

In PostgreSQL, you must be the table owner (or a superuser) to create an index on a table.

There is no separate GRANT permission (such as GRANT INDEX) that allows a non-owner to add an index.

Since Sharon is the owner of local_derived.marc__t table, she will be able to create an index for it.

Table folio_source_record.marc__t is owned by metadb_user account (whichh is the account which the metadb service runs as )
Only metadb_user or the superuser in postgresql would be allowed to create indexes for this table.

We would suggest discussing any new indexing with the metadb developers before making adjustments to any tables which are owned by metadb
(folio_source_record.marc__t )

Please let me know if you have any questions.

Cameron Viveiros
FOLIO Customer Account Specialist
EBSCO Information Services
978-414-0645
cameronviveiros@ebsco.com

This message and its contents are confidential. If you received this message in error, do not use or rely upon it. Instead, please inform the sender and then delete it.


--- Original Message ---
Hi Hosting Team,
We have been having trouble with the folio_source_record.marc__t table, so we set up a query to recreate this table in the local_derived schema. The table works, but queries against it run slowly. I would like to try indexing the table to improve performance. Is it possible for me to index tables with the permissions I currently have on my z_slm5 user account for our Metadb reporting database, or is this something you would need to add?
All the best,
Sharon



6455456 Cornell Metadb: MARC _ _ t table issue: Multiple srs IDs associated with same instance IDopen

 

 6390448  Cornell Metadb: connection via Power BI Desktop failingunresolved



Request to add hostname to SSL certificate SAN for Metadb (Power BI connectivity issue)
Message sent onApril 30, 2026 at 08:18 AM PDT

From:Sharon Markus

Hosting Team,

As you are aware from previous ticket entries, we are currently unable to connect to our Metadb PostgreSQL reporting database.

After some research into the issue on our end, we believe the connection cannot be made from Power BI Desktop due to a SSL hostname validation failure.

The server certificate presented by the database endpoint includes only the AWS RDS hostname:

CN: metadb-scnl.c51bi8byxdg6.us-east-1.rds.amazonaws.com

SAN: metadb-scnl.c51bi8byxdg6.us-east-1.rds.amazonaws.com

However, our connection is made using the EBSCO-provided hostname:

metadb-db-cornell.folio.ebsco.com

Because this hostname is not included in the certificate’s Subject Alternative Name (SAN) list, Power BI rejects the connection during SSL validation.

Please update or reissue the SSL certificate for the Metadb endpoint to include the following hostname in the SAN field:

metadb-db-cornell.folio.ebsco.com

Ideally, the certificate should include both:

metadb-scnl.c51bi8byxdg6.us-east-1.rds.amazonaws.com

metadb-db-cornell.folio.ebsco.com

Other tools (e.g., DBeaver) can connect due to relaxed SSL settings, but Power BI enforces strict hostname validation. This change is required for secure, standards-compliant connectivity from Power BI.

Please let us know when this update has been applied or if any additional information is needed.

All the best,

Sharon


P2 SI # 4809078 : Cornell Metadb: connection from PowerBI to Metadb still not working
Status

Working
Case Number

6596013
DETAILS
Case Subject
P2 SI # 4809078 : Cornell Metadb: connection from PowerBI to Metadb still not working
Case Number
6596013
Description


Hosting Team,
Please escalate this issue as a high priority.

Our network connections from PowerBI to the Cornell Metadb reporting database are still not working. Please see related previous case on this issue SI 4404657 | Cornell Metadb: connection via Power BI Desktop failing, which was closed without resolution.

Our reporting team needs to be able to connect to the Cornell Metadb reporting database from Power BI. I am trying to make a connection from my computer with a static IP address that has already been whitelisted for access to our Metadb database for access via DBeaver and Tableau. I am able to successfully connect to Metadb from those applications.

When I set up a connection using the PostgreSQL database connector in Power BI Desktop, I get the following error message:

"Unable to Connect. An error happened while reading data from the provider: 'The remote certificate is invalid according to the validation procedure.'"

My PowerBI connection details are:
Server: metadb-db-cornell.folio.ebsco.com:5434
Database: metadb

In answer to issue SI 4404657, you provided us with some generic troubleshooting information. We have tried the solutions offered in messages connected to this ticket and none of them have worked. We must get this connection working. There are other institutions on the FOLIO Project who are using Metadb with PowerBI successfully, so this should work.

As a next step toward resolving this issue, please provide us with answers to the following 2 questions:

Question 1 - Are you using an alternative hostname for our Postgresql Server that runs the Metadb software, one in the "rds.amazonaws.com" domain? Using the alternative hostname, instead of the one we usually use, might result in success by having the name the client is expecting (PowerBI native Pg drivers) match the one the server is transmitting, if it turns out those aren't the same when using the hostname we usually use.

Question 2 - In what region does the AWS RDS Postgresql Server run? In other words, which certificate bundle should we choose to install from this list of Amazon RDS Certificate Bundles?
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL.html#UsingWithRDS.SSL.CertificatesDownload


If the next set of answers does not get us any further, we will need to arrange a Microsoft Teams or Zoom meeting with one of your server administrators so we can troubleshoot this issue in real time.

All the best,
Sharon Markus
Service Issue Number
SI-4809078
Institution
Cornell University Library
Product
FOLIO
Requester
Sharon Markus
Area of Support
FSE Hosting Issue
Assigned To
Whitney Jordan

-------

Thank you for contacting EBSCO.

Your EBSCO Customer Support Case Number and Title are: 6390448 - "SI 4404657 | Cornell Metadb: connection via Power BI Desktop failing".
_________________________________________________________________

Hello Sharon,

I've found someone with a similar issue online, which they solved. Here is the issue:
https://community.fabric.microsoft.com/t5/Desktop/The-remote-certificate-is-invalid-according-to-the-validation/m-p/532504#M249591

Solution:
https://community.fabric.microsoft.com/t5/Desktop/The-remote-certificate-is-invalid-according-to-the-validation/m-p/532504#M249591

Cameron Viveiros
FOLIO Customer Account Specialist
EBSCO Information Services
978-414-0645
cameronviveiros@ebsco.com

This message and its contents are confidential. If you received this message in error, do not use or rely upon it. Instead, please inform the sender and then delete it.

--- Original Message ---
Hi Cameron,

I tried the settings you mentioned and was not able to successfully connect to Metadb from PowerBI on my computer that has a static IP address that is whitelisted for use with Cornell's Metadb reporting database.


I am attaching the specific login configurations I tried as a Word document.


Any other ideas?


All the best,

Sharon

---

Cameron Viveiros
Emailauto-response@ebsco.com
To: s9001366 Cornell University Library : Sharon Markus


The Metadb PostgreSQL endpoint does not use a self-signed or internal CA certificate.
It uses the standard AWS RDS public certificate chain, which should be trusted.
Tools like DBeaver and Tableau connect successfully because they automatically set SSL options 
and handle the AWS RDS certificate chain correctly. 
Power BI Desktop requires additional parameters; otherwise, it rejects the connection even with a valid certificate. 
Please try the following in Power BI Desktop’s PostgreSQL connector 
under Advanced Options: SSL Mode=require Trust Server Certificate=true 
This forces encrypted transport but bypasses Power BI’s strict certificate checks.