-
Notifications
You must be signed in to change notification settings - Fork 1
Meeting Agendas
- Housekeeping (recap)
- Collaboration spaces
- Platform support: email Alicia (ito-ra ät oceannetworks.ca) or book a 1-on-1 appointment here.
- Meetings
- Today's goals and outputs
- Definitive list of challenges
- Definitive list of (HMetS-relevant) repository characteristics
- Discussion
- Group’s feedback (general)
- Challenges
- (HMetS-relevant) repository characteristics
R - Robert Downs S- Sarah Reay J - Juanle Wang K - Karen Payne A - Alicia Q - Qi Xu
-
Lessons learned vs Challenges and Opportunities R: didn’t see them as lessons learned as written. TBD what exactly “opportunities” entails. Feeling was, wait and see what people do in terms of additional revisions, changes will give insight into where we’re going with this paper as a team. At the moment, not entirely sure where we’re going as a team
-
Platform R: Been able to use collab platform, found it time-consuming, dealing with platform, but it’s doable J: Couldn’t access at the moment (doesn’t have account number), will follow up R: One approach that helps: generate pdf and navigate that way is easier. Next steps: try overleaf (using rich text), give feedback, may need to find alternative (i.e. sharepoint) R: Clean the document of tracked changes
-
Overleaf link supplied onto GitHub
-
List of Challenges we WANT to talk about, give recs for Combine: Original users, reach new ones; Making data assets more visible to more diverse uses Enable proper reuse, attribution, citation Coordinating standards adoption - too complex? R: Frame as contributing to standards, adopting separate Keep these two ideas together, label it as something more general, describe in the text “Standards Coordination”: coordinating externally or internally, discuss phases of adoption Project funding and resources - Too vague? Keeping track of who is using products Balancing openness and data protection Limitations of a harvesting strategy for discovery
Moving forward:
- Alter headers and work within these ideas
- List of features of repository characteristics that impact community
- Intro: Our outputs so far.
- Overview: Collaboration Framework Fees may be increasing for the DS journal; Juanle to reach out to board Bob: having track changes on in the document, removing silos, may need more flexibility at the expense of formality Check-ins in a structured way Bob: depends on progress of paper. Karen: we can always remove meetings later
- Paper: Proposal and contents
- Sections
- Methodology Alicia: Close reading, narrative, empirical, qualitative
Karen: synthesis approach with the landscape
Bob: Social and physical science background, interdisciplinary collaborations, interested in new methodologies
Juanle: Repository, FAIR principle, harvestable metadata. Compile different use cases and find a good solution
Simon: uptake and usage of data in GS data, retiring soon, may be replaced with a new contact: Sarah Grey
Qi Xu: No concerns about the organization
Aude: to go back to historical papers, to reproduce derivation workflow, to compare with historical values (hopefully identical) and to add as much pieces of information as possible in metadata
Task definition and assignment
- Tools: Using Overleaf with the HMetS Writing Group 3-minute explanation
Other options to add your content to draft
Bob: concerned about losing changes, may want to verify change tracking mechanisms, Alicia to follow up with how changes are stored in overleaf
Action items: Alicia sends paper draft and overleaf access instructions to group