Sherry Lake (May 15 2025 at 13:34): Sherry Lake (May 15 2025 at 13:34):Continuing conversation from google groups: https://groups.google.com/g/dataverse-community/c/Yw9F63MHMUQ
After upgrading to V6.6, we were getting errors in our server.log. Before I reindexed "all" (clear index), I created a new dataset. It didn't show up in the listing. The direct URLs work, shows draft record and one published, but nothing in the collection list.
So I ran api/admin/index/clear - and then reindex. And still getting the errors reported in google.
BUT now nothing shows in any collection.....
Help! Luckily this is my test server.
Philip Durbin 🚀 (May 15 2025 at 13:37):Did you do all the Solr-related upgrade steps in https://github.com/IQSS/dataverse/releases/tag/v6.6 including switching to Solr 9.8.0?
Sherry Lake (May 15 2025 at 13:39):I think so..... our solr is on a different box so my admins use terraform?? to push the updated schema.xml and solrconfig.xml
Sherry Lake (May 15 2025 at 13:39):I know we did that part.... but hm..... let me check on the actual upgrade.
Philip Durbin 🚀 (May 15 2025 at 13:40):Awesome, thanks
Sherry Lake (May 15 2025 at 14:16):Still waiting to hear from my sysadmin.... but question while I wait....
In the release notes, since UVA has additional metadata blocks, we do not use the schema.xml file in step 10 (of 6.6 release notes) downloaded via "wget"?
Instead we run the update-fields.sh command on our schema.xml.
That might not be what I did.....
Philip Durbin 🚀 (May 15 2025 at 14:22):Yes, that's something to check.
Sherry Lake (May 15 2025 at 17:08):solr was updated.
Trying stop/starting solr.... when Tim (the sysadmin, not the cat) has a break.
Questions about the solr section in release notes......
The schema.xml that is downloaded (wget) should it go directly to the directory. ..../solr/collection1/conf/
But if solr 9.8.0 is already installed, do we have to do the wget?
By installing solr 9.8.0, we should already have the "schema.xml" file and would not need to do the "wget", or do we really need the ones from V6.6 of dataverse (wget command)?
Then... with this new schema.xml file in it's correct place (either from wget or from install).
I would then run the update-fields.sh script - and it would update (in place) the new schema.xml file (in our solr/collection1/conf directory) using the contents of our solr "index" command (api/admin/index/solr/schema) to get our customized metadata parts in the new schema.xml?
Because re-index of solr hasn't happened at this step in V6.6 upgrade, the index has our customized metadata block?
Trying to understand what is supposed to happen, so I might figure out what I did. So I don't make the mistake on production!
Philip Durbin 🚀 (May 15 2025 at 17:30):Correct, https://guides.dataverse.org/en/6.6/installation/prerequisites.html#solr does explain how to get the schema.xml file.
Sherry Lake (May 15 2025 at 18:37):Ok, datasets now showing. Not sure what the problem was, but Tim
"reloaded the core" (not sure what that is)
and reindexed.
Seeing existing datasets and new ones.
Philip Durbin 🚀 (May 15 2025 at 18:42):Fantastic! Go Tim! 
Philip Durbin 🚀 (May 15 2025 at 18:45):For Dataverse there's only one core and we call it "collection1".
Notification Bot (May 15 2025 at 19:33):Sherry Lake has marked this topic as resolved.
Last updated: Oct 30 2025 at 06:21 UTC