Latticegrid users group forum 2011
Agenda for the meeting:
- What is LatticeGrid
- How to install
- How to configure
- How to load
- Visualization
- Sharing
Summary of the scope, mission, and advantages of LatticeGrid are, particularly for NCI designated Cancer Centers.
The direct goals of LatticeGrid are to:
1. Represent the Cancer Center Members by Program
2. Represent all publications by Cancer Center Members
3. Provide tools for identifying publications are cancer relevant and should be included in the CCSG submission.
4. Provide tools for cancer center leadership, including program leaders, for identifying important publications among the membership.
5. Provide CCSG-formatted publication reports for the overall cancer center and each program.
From a network analysis standpoint, LatticeGrid is designed to:
1. Identify the network of collaborations that currently exist in a biomedical research organization through
co-authorship, participation on clinical studies, or through joint participation on funded projects.
2. Highlight the expertise and existing collaboration patterns for an individual in that organization.
3. Analyze changes in the pattern of collaboration for a given individual, virtual organizational unit,
academic unit, or other organizational structure over time.
4. Facilitate the application of this information to the promotion and support of intra- and inter- institutional collaboration.
From a configuration/installation standpoint, rather than asking adopters to install from GitHub (the official repository), and configured VM with a fully configured CentOS installation of LatticeGrid will be made available.
Action items, broken into 'easy', 'not so easy' and 'really hard'
Easy is not necessarily 'Quick" but means the data, structures, and capability is already in LatticeGrid or else the use case and analysis of the implications has been completed and the activity required is really clear. Not so easy implies some change in the behavior of LaticeGrid or else something that I think needs more analysis before it is implemented Really hard means architectural change or more pervasive change for LatticeGrid or else it needs a lot more analysis and discussion before implementing the change
[documentation] Provide links to the group for editing the LatticeGrid Wiki
[interface] Provide a web interface for changing/adding PubMed search terms to an individual investigator
[interface] Provide a web interface for limiting PubMed searches for an individual investigator to the institution
[reporting] Add Journal Impact Factor to all CCSG-styled reports
[reporting] Add Journal Impact Factor percentage by year and program
[interface] Provide a web-based interface for adding and deleting programs
[interface] Provide a web-based interface for adding and deleting individual members
[interface] Provide a web-based interface for changing the programmatic affiliation(s) of members
[interface] Provide a way to download an endnote library for all the publications by an investigator
[interface] Provide a way to download an endnote library for all the publications by program
[logic model] Provide a general authentication framework that is abstracted from the details. (AuthLogic does this)
[interface] Provide an interface for adding publications without a pubmed id (how to resolve duplicates if the publications ends up later in PubMed - can we use DOI for this?)
[import, schema] Add a way to mark program affiliations as primary or secondary - only include primary affiliations in the CCSG reports but still show secondaries on the member publications pages
[import, schema, interface] Represent core facilities
[import, schema, interface] Represent core facility users
[import, schema, interface] Provide a way to mark if a member's publication involved the use of a CCSG supported Core
[interface] Enable drill down in the Impact Factor reports to show precisely the publications that make up the count listed for a given journal in a given year.
[interface] Provide impact factor reports by program and date range
[interface, schema] Provide a mechanism for approving changes (use case is clear - how to make it happen is not - it means at the very least having user roles in Latticerid)
[interface, logic model, schema] Provide an interface for creating 'what if' scenarios that are 'sticky' - that is, create a program affiliation scenario for the entire cancer center and analyze the inter/intra programmatic activities
[project structure] Modify the project so others can more productively contribute code and ideas
Regina pointed out that all the ISI journals should be crosswalkable to PubMed through the ISSN number, and that there are two ISSN numbers in PubMed, with the 'linking' ISSN the same as the ISI ISSN. There are a number of journals whose names are not identical in the two sources that this should allow fully automated crosswalks.