The case study I read was conducted by the Digital Curation Centre (DCC), and can be found at: http://www.dcc.ac.uk/docs/publications/case-studies/SCARP_EMAP.pdfThe case study was conducted on the digital curation of the Edinburgh Mouse Atlas Project (with the obligatory acronym EMAP.) EMAP's primary goal is to create and manage a mouse embryo gene database (which got its own acronym -- EMAGE.) The case study conducted by the Digital Curation Centre seemed to me to be a good example of the case studies we will be conducting during this class.
To find out how the EMAP was organized and curated, the author visited the website and conducted interviews, as well as attending meetings at the project. She compares their process and final product to the DCC Curation Lifecycle (DCCCL?).
The DCC Curation Lifecycle is a Digital Curation Centre diagram depicting the process of curating digital objects. From conceptualization of the item to transforming for preservation, curating, describing, and involving the community, the lifecycle is complex to say the least, and I'm unclear on how quantitative a comparison to such a chart could be. The image below depicts the cycle; you can view the original here: http://www.dcc.ac.uk/docs/publications/DCCLifecycle.pdf

Although the case study using the curation lifecycle of EMAP states that the EMAGE database is the first scientific visualization of gene-expression (what -- no other spatial maps of Mouse genes?) the study also reported several areas that need further problem-solving.
1. Copyright inhibits use of needed images.
2. New ways of displaying data need some standardizing.
3. Data entry methods are slow and at times unreliable.
4. Quality Assurance is not, in fact, assured
These four puzzles struck me as being probably very common problems in creating infrastructure for projects, and carrying out almost any digital curation project successfully.
Quality Assurance in particular has historically been a -- perhaps purposefully -- overlooked area in hardware and software development.
The author and editors of this paper lean toward believing that data can and will be shared in the life sciences, and they write, "Recent life sciences studies, such as the Joint Data Standards Study5 (2005), have demonstrated the value of sharing and re‐using data." They believe that publicly funded projects will therefore continue to build tools with this data sharing, and that the main problem to overcome is the planning for creating the "cyberinfrastructure" for all that data.
While they may not be entirely correct that scientist will willingly share their data, I agree that standardization and planning must continue before useful tools and projects such as EMAP can spread to a community beyond determined and/or specialist users.
