That’s according to Dr Jason Gush, who is responsible for the Insights and Evaluation Programme at the Royal Society Te Apārangi, and a member of the NZRIS Stewardship and Oversight Group (NSOG).
Jason has been involved in NZRIS since 2016 when the Research, Science and Innovation Domain Plan – which identified the need for a nation-wide research information system – was released.
He says despite the lengthy lead-in time to the new system, he can see real progress is being made and is enjoying the team approach that’s been taken.
“There has been a good ‘get together’ feeling about this, people have been engaged and there is
something of a community that has been created. The NZRIS team at MBIE has been responsive and it’s been a good crew to work with.”
The in-depth involvement that Jason has had with NZRIS means he has valuable insights and advice for other research organisations that are not yet familiar with NZRIS.
“The first thing to remember is that NZRIS is not just going to be a public website – it will also include a secure data warehouse facility that data providers can access through a user interface that is protected and unique to them. This means that NZRIS is effectively providing organisations with a secure store in which they can hold their data, so it’s definitely an opportunity.”
He
acknowledges that it can be difficult for an organisation to know where to start when it comes to getting their data ready.
“As a new organisation, I would first look at what your obligations are. For example, if your organisation funds research rather than undertakes it, then you’re likely to fall into the ‘Asset Pool Manager’ category. This means that the data you submit to NZRIS will be about the funds you manage and how you distribute them.
“It’s important to focus on the mandatory data and what needs to go in these fields. The mandatory data is the minimum set of data that is required. It’s also important to remember that to start with, the only data NZRIS requires is data that is already public data anyway.
“Even though the focus should be on the mandatory data that is required, as data will not be accepted into the system without these, I do recommend that organisations keep in mind other types of data they may need to provide in future. For example, data about project activity or type of activity is data that NZRIS will accept. Even though organisations will often collect this data as part of the application process, it’s not something that is necessarily kept in mind beyond the application process. So it’s good to think about starting to capture that kind of data now.”
Jason is also keen on the new NZRIS GitHub site, available at https://github.com/new-zealand-research-information-system, which is a shared space aimed at people working through the NZRIS data specifications and wanting to raise technical issues or ask questions. More detail on our Github site can be found in the previous article.
“The new GitHub site is great, because it’s a real-time forum where we can come together as a community to raise any issues we find, and have them addressed. The NZRIS team has been responsive and I think it’s working well,” Jason says.
If you’d like to talk to Jason more about his views and experience with NZRIS, feel free to get in touch with him at Jason.gush@royalsociety.org.nz – he’d be happy to hear from you!