scholarly journals Completing the data life cycle: using information management in macrosystems ecology research

2014 ◽  
Vol 12 (1) ◽  
pp. 24-30 ◽  
Author(s):  
Janine Rüegg ◽  
Corinna Gries ◽  
Ben Bond-Lamberty ◽  
Gabriel J Bowen ◽  
Benjamin S Felzer ◽  
...  
2018 ◽  
Vol 23 (4) ◽  
pp. 555-571 ◽  
Author(s):  
Silke Roth ◽  
Markus Luczak-Roesch
Keyword(s):  

2021 ◽  
pp. 85-94
Author(s):  
Rob Kitchin

This chapter focuses on the role of finance and the politics of collaboration, charting the development of the Digital Repository of Ireland (DRI). DRI have been beset with institutional politics concerning its framing, development, and operation. The future funding issue was just the latest example in a long list of fraught exchanges that could be traced back to its original conception and funding mechanism. The DRI was born out of a funding opportunity, but seemed destined to die due to a funding failure. Without a political solution, the data life cycle would turn full circle much more quickly than initially anticipated. Unless there is a means of covering the costs for labour, equipment and other essential inputs, data are not generated or stored, and thus cannot be used or shared. Even in open data projects, the data might be free to use but they were not free to create, or to process and host.


2012 ◽  
Vol 14 (3) ◽  
pp. 14-34
Author(s):  
Roger Clark ◽  
Jonathan Wingfield

In 2006 AstraZeneca (AZ) executed a strategy to centralise all biochemical screening activities within one of its Research Areas, into a single team. This team had the remit to deliver data faster and more consistently, whilst reducing the FTE’s deployed against such activities. Keeping the team small, AZ hoped to facilitate more flexible use of resources, remaining agile enough to respond to changing business demands; however this centralised approach brought with it a fresh set of challenges, not least of which was information management. This review describes a successful LIMS implementation within AZ (who deployed a customised COTS solution in just four months). It outlines the steps taken over the initial system development life cycle and highlights the requirement for dedicated in-house resource (with intimate domain knowledge) coupled with experienced vendor personnel. It goes on to explore the requirement for continued evolution of the system and the challenges this posed.


Sign in / Sign up

Export Citation Format

Share Document