Yes, @TroveAustralia has changed. It had to – the technology was out-of-date, inflexible, and difficult to maintain. No change would have meant more problems down the track.

If you’re finding it difficult to adapt, here’s some things you can do...
Ask for help. There are often multiple ways of achieving the same end. If you tag @TroveAustralia here, then I and others might be able to suggest alternative approaches.
If you find a problem report it to Trove support. Also keep an eye on the ‘Known issues’ ( https://trove.nla.gov.au/about/what-trove/technical-ecosystem/known-it-issues) and ‘Updates’ ( https://trove.nla.gov.au/about/what-trove/technical-ecosystem/trove-system-updates) pages to see what’s being worked on. One of the benefits of the upgrade is that it’s now easier to make changes!
Share your methodologies! It’s really hard to get good information on how people actually use complex systems like Trove. How does Trove fit into your research practice? What makes it harder, and what would make it easier?
Remember that the web interface is not (and cannot be) everything. There are other ways of using, sharing, aggregating, and analysing Trove data. See the #GLAMWorkbench for examples. https://glam-workbench.github.io/ 
We cannot expect GLAM organisations to do everything. Yes, criticism is important, but so is experimentation, flexibility, and generosity. We can find solutions together!
There’s also a useful FAQ explaining some of the recent Trove changes here: https://trove.nla.gov.au/frequently-asked-questions
And here’s a related question from this morning… https://twitter.com/wragge/status/1299510646082420736
You can follow @wragge.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled: