But this information should should be in the public API. The data’s somewhere – there’s an internal API that’s used to generate lists of issues in the browse interface and I’ve scraped this to harvest issue details. There is no comparable way of retrieving a list of digitised journals, or the issues that have been digitised. You can use it to get a list of available issues for any newspaper. The API includes a newspaper endpoint that provides data on all the newspapers in Trove. We can get an idea of what’s missing by comparing the digitised journals to the newspapers. The digitisation process has generated new metadata describing these resources, but most of this is not available through the public API. In recent years, the NLA has digitised huge quantities of books, journals, images, manuscripts, and maps. There’s no way of transferring your questions – you need to start again.Įxpand the metadata available for digitised resources other than newspapers. But, except for the newspapers, there is currently no one-to-one correspondence between searches in the web interface and searches using the API. Some of these questions might be answered by downloading data from the API for analysis or visualisation. Why does this matter? The web interface allows researchers to explore the collection and develop research questions. The API, however, is still organised by zone and knows nothing about these new categories.
TROVE HACKS TOOL UPDATE
The Trove interface update in 2020 reorganised resources into ‘categories’, replacing the original ‘zones’. Researchers should be participants in these processes, not consumers.Īnyway, here’s my current wishlist… APIs and dataīring the web interface and main public API back into sync, so that researchers can easily transfer queries between the two. Building tools through networks of collaboration and information sharing based on good quality data offers much more.
TROVE HACKS TOOL SERIES
A series of one-off tools for researchers might be useful, but the benefits will wane. This is the second reason I think the data is critically important – our focus should be on developing communities and skills, not products. There needs to be an ongoing conversation between data providers, research tool makers, and research tool users. Many of these questions will arise as people try to make use of the data. There will be questions about priorities, about formats, about delivery, about normalisation and enrichment. But, of course, it’s never just a matter of OPENING ALL THE DATA. First because public access to consistent, good quality data makes all other things possible. My focus is again on the data this is for two reasons. I created a list of possible API improvements in my response to last year’s draft plan, and thought it might be useful to expand that a bit, and add in a few other annoyances, possibilities, and long-held dreams. The ARDC will be holding two public roundtables, on 13 and 20 May, to gather ideas. This is a chance to start from scratch, and think about the types of data, tools, or interface enhancements that would support innovative research in the humanities and social sciences. The ARDC is collecting user requirements for the Trove researcher platform for advanced research.
0 kommentar(er)
