Core 6 Timeline Notes
From NAMIC Wiki
Home < Core 6 Timeline Notes
- Create a collaboration methodology for NAMIC
- Work with PIs and Management Core to develop a selection process for identifying collaborators and defining the scope of the collaborations.
- Develop a set of guidelines to govern the collaborations including but not limited to expected authorship of publications, data sharing, intellectual property ownership, grant citation, and other academic recognition.
- Provide on-site training of individuals at collaborating sites using materials and educational objectives defined in collaboration with the Training Core.
- With the Service Core, develop a web site infrastructure to capture the results of the collaborations.
- Facilitate communication between NAMIC developers and wider research community
- Work with the Training Core to develop materials describing NAMIC technology to enhance user proficiency.
- With the Training Core, participate in scientific meetings to encourage adoption of NAMIC technology by the community.
- Document interactions with external researchers and communicate the information to NAMIC developers to help define priorities and development directions.
- Coordinate publication strategies by serving as a point-of-contact for editors seeking contributions and by documenting potential publication topics and encouraging NAMIC developers to create manuscripts.
- Develop a publicly accessible internet resource of data, software, documentation, and publication of new discoveries
- With the Service Core, maintain an on-line repository of NAMIC related publications and presentations including supporting data and code where appropriate.
- With Training Core, maintain an on-line repository of NAMIC tutorial and training material.
- Provide an index and a searchable database to assist users in finding the NAMIC resources and links to related external resources.
- With the Service Core, develop automated feedback systems that track software downloads and gather user feedback in order to better understand the community’s reactions to the software.