diff --git a/content/europa/meeting_notes/1.19.23.md b/content/europa/meeting_notes/1.19.23.md
new file mode 100644
index 0000000000000000000000000000000000000000..cb122875facb5bf254342dfdff50231986bf8711
--- /dev/null
+++ b/content/europa/meeting_notes/1.19.23.md
@@ -0,0 +1,55 @@
+---
+date: '2022-11-17'
+title: '2022-12-15 Working Meeting (DRAFT)'
+---
+
+{{< meeting-notes >}}
+
+## Meeting Link
+When 8PM GMT, 12PM PST, 1PM MST
+[https://jpl.webex.com/jpl/j.php?MTID=m3c96c22ed8e335e55dbd40c9084e3763](https://jpl.webex.com/jpl/j.php?MTID=m3c96c22ed8e335e55dbd40c9084e3763)
+
+## Attendees
+- Mike Bland
+- Robin Fergason
+- Cynthia Phillips
+- Jay Laura
+- Paul Schenk
+
+## Agenda
+- LPSC Abstract submitted.
+ - Very happy to hear from IAU re: longitudes. We can get them on the schedule.
+ - Need to socialize why the decision that was made was made.
+- Voyager data
+ - Mike sent data to the person who was asking for these data got a pre-release product.
+ - Still on the todo list.
+ - Just finishing off the metadata for the Europa DTMs. Voyager after that.
+ - Discussion of tutorials to support the Europa data releases.
+ - For tutorials need to decide what we want and have someone assigned to do it.
+ - DTM and image align. Would be a GIS style tutorial. How to throw them together, make some profiles.
+- Quick discussion of SPD-41a and copyrights.
+ - We'll keep our license selections to support the need for attribution for data providers.
+- Horizontal datum / Juno:
+ - Abstract in for LPSC (Juno part); committed to do the work. Cartography and topography discussed with good results.
+- No discussion at the upcoming Europa Clipper PSG meeting.
+ - No spot in the agenda. It is quite full and more working interactions.
+ - Instead, we should present this at a monthly science team meeting.
+ - Let's present Monday, March 6th at noon PST.
+ - How close are we to having a horizontal datum? We will adopt the datum.
+ - Vector data - we have standards for vecvtor data. USGS is willing to host these under the Europa SDI.
+ - We are ready for your data.
+ - We are ready to help you host and advertise your data in a compliant way.
+ - Working to coordinate with JUICE. Who? Mike might have some contacts. Cynthia too.
+ - Project science might be a good initial PoC.
+- Data can be uploaded with an abstract.
+ - Recommendations about what those data can and can not be. This would be for meeting organizers.
+-
+
+
+## Notes
+
+## Action Items
+- Jay: How to find Europa data (spatial / temporal) and how to download it.
+- Jay: Get in touch with someone at JUICE.
+- Jay: Draft some sort of intake for new data or services that we can integrate.
+- Robin: Sharing agreement. We have a science base agreement. We can use that verbatim?
\ No newline at end of file
diff --git a/content/europa/meeting_notes/12.15.22.md b/content/europa/meeting_notes/12.15.22.md
index ac9c4ae1d5a34cc960f4e6a83277c6ed0fb8a1a0..93a9eb30c25ade8a18148dc5affd1c23d1941fb0 100644
--- a/content/europa/meeting_notes/12.15.22.md
+++ b/content/europa/meeting_notes/12.15.22.md
@@ -13,8 +13,67 @@ When 8PM GMT, 12PM PST, 1PM MST
## Agenda
- Prep for LPSC / PSG rollout. Initial list of tasks.
- -
+ - Do we want to request time? At what level?
+ - Requesting at the geology working group level is probably fine.
+ - Perhaps contact the WG co-chairs to see if they have space.
+ - Larger group would also pull in geodesy, etc. where they are charged with thinking about coordinate systems, standards, etc.
+ - If discussing in geology, make sure geodesy knows.
+ - Time?
+ - 15 minutes is likely enough
+ - Who is going to be in person?
+ - Mike will be there and can present. If in person, has to be arranged ahead of time. Paul - not sure if he is in-person.
+ - Also Cynthia
+ - Who else will be in person?
+ - Other should dial in?
+ - Cynthia will ask for some time and if others can register in advance and attend.
+ - Content or Clipper PSG (Feb 6th-10th):
+ - The next step - this isn't just one set of data, this goes beyond that.
+ - We have governance and standards.
+ - We are now looking for data creators and/or data providers who have data that we can help to get turned into analysis ready and provided to the community.
+ - NIMs data?
+ - Reach out to them. Are any on clipper?
+ - Mike Milaska(sp?)
+ - Covers Callisto as well
+ - We've hosted all the Galileo data, but haven't done anything with the Voyager data.
+ - Astrogeology has the Voyager data and can release it.
+ - Paul might have NH data?
+ - Juno?
+ - Data Message (We can make this case at LPSC; this can be a shorter message.):
+ - If one has ~Juno~ Europa data and wants to process it and describe the processing, we have standards that, if you meet them, they will interoperate with other Europa SDI data.
+ - If you have ~juno~ Europa data that you process and need help bringing it into compliance with the Europa SDI, reach out.
+ - If you have servers with data and want to bring them into compliance with the Europa SDI standards, we want to help.
+ - The big lift for creators is that we need your help with documentation! What are the data usable for? What does one need to be careful about?
+ - SPD41a - are we helping folks come into compliance?
+ - We might need to adopt a standard that data will have a DOI?
+ - Need to embrace the data ecosystem - this is an effort to embrace and support the data ecosystem.
+ - Message about how we would be supportive of the Europa Clipper missions.
+ - This is the most important message.
+ - How can we specifically support the clipper mission?
+ - Two general ways we are supportive: (1) before arrival and (2) after arrival. (1) supports the detailed planning that is already underway, e.g., EIS targeting and knowing where they are is exceptionally important. Paul's vs. Mike's data means things are in different locations. (2) once the data are in the PDS making sure that that data is as usable as possible for clipper AND non-clipper team members is supported. Europa SDI makes sure that data plays well with existing data sets and future data sets.
+ - Clipper is also working on building an internal team tool for planning and access to new data on arrival. The Europa SDI is not the same as the EGAS.
+ - Having this tool read Europa SDI compliant data means that any existing data under the Europa SDI can be ingested.
+ - The tool is still 8 years out?
+ - The Europa SDI exists now and can support both the external community and the team. Tools built against the standards means that compliant data automagically works in that tool.
+ - Focus has been on what the tool needs to do.
+ - We are interested in helping ensure that the input data are standards compliant AND the data are broadly available. We are not EGAS, we care about the underlying standards.
+ - Avoid having multiple different base maps, different datums, etc. Consistency is exceptionally important.
+ - This is a conundrum with Europa data - not enough to worry about, yet.
+ - PDS support for the ecosystem discussion.
+ - PDS4 - can we do sidecars / sidestep to geospatially enable.
+ - Vector data
+ -
- Draft LPSC abstract.
+ - Working on it.
+- Good STAC Matt Hansen talk today.
+ - Talk about footprints.
+- Voyager data
+ - Jay will release it. Mike will think about what is needed to get it to Jay.
+- Does an SDI working group talk about the tools?
+ - Sure, but it can't be prescriptive.
+ - Creators need to document.
+ - Providers need to mediate disagreements.
## Notes
## Action Items
+- Cynthia is drafting an email. Asking for 15 minutes with everyone. Backup to the geology group.
+- Voyager data: Jay will release it. Mike will think about what is needed to get it to Jay.
\ No newline at end of file
diff --git a/content/moon/meeting_notes/01.12.23.md b/content/moon/meeting_notes/01.12.23.md
index c4e51476ee922f9b188720dcd90966d1e77377b6..58d766b5f748c8929ed335ce6b6ef734838fb479 100644
--- a/content/moon/meeting_notes/01.12.23.md
+++ b/content/moon/meeting_notes/01.12.23.md
@@ -9,7 +9,11 @@ title: '2023-01-12 Working Meeting'
No dial in number yet, sorry!
## Attendees
--
+- Robin Fergason
+- Laz Kestay
+- Ross Beyer
+- Julie Stopar
+- Jay Laura
## Agenda
- Governance document review
@@ -18,10 +22,33 @@ No dial in number yet, sorry!
-
## Notes
-
--
+- Context:
+ - The governance model is fairly generic. Modelled after Europa. For Lunar specific changes we should incorporate those. Code of conduct is modelled off the Europa SDI.
+ - The strategy document is a seed for discussion based off the Europa model.
+- Strategy document:
+ - This is not as mature as the other documents.
+ - Share that out as a word document.
- Open floor
+ - List of data / providers that LEAG is worried about.
+ - Don't these missions all have DMPs for these data.
+ - Perception: many of these missions have budgets that are tight so getting the data into a PDS compliant format can be challenging.
+ - Where can we help with this problem?
+ - Reminder for NASA that data may need additional funding in order to get these data.
## Action Items
--
\ No newline at end of file
+- Jay: Clean, add context, reorganize, executive summary, and solicit for feedback.
+- Jay: Post the code of conduct for discussion.
+- Jay will send a list of names to Robin and she will get the docs out to the folks for review.
+- Jay: Ping Amy - can we get a list of data that is of concern?
+- Jay: Ping Brad re: MAPSIT - more info. Are we a candidate interface for standards between LEAG / MAPSIT?
+
+Next Agenda:
+- MAPSIT / LEAG updates
+- LPSC - what do we want to have? Input on poster. (Jay - start the poster.)
+- Code of Conduct - ratified
+- Strategy Documents
+- Any discussion of standards
+
+## Next Meeting
+Feb 9th @ 2PM MST.
diff --git a/content/moon/meeting_notes/12.8.22.md b/content/moon/meeting_notes/12.8.22.md
index cf5c8fd450ed63d9b5e5ab1ca1ff2299d78e5b56..a31bcac9ce438ab608109ed73f0fc4db88ff5998 100644
--- a/content/moon/meeting_notes/12.8.22.md
+++ b/content/moon/meeting_notes/12.8.22.md
@@ -94,4 +94,5 @@ No dial in number yet, sorry!
## Action Items
- From last meeting:
- All: Review governance documents. Async discussion as appropriate. Goal is to be able to discuss in person anything where consensus is hard to find in January.
- - All: Think about an LPSC abstract (due 2 days before our January meeting). Likely a great opportunity to publicize our work. Discuss async if possible to keep space for standards discussion. I (Jay) can write a lunar/europa SDI one or a separate lunar and Europa one. Anyone on here can first author this too!
\ No newline at end of file
+ - All: Think about an LPSC abstract (due 2 days before our January meeting). Likely a great opportunity to publicize our work. Discuss async if possible to keep space for standards discussion. I (Jay) can write a lunar/europa SDI one or a separate lunar and Europa one. Anyone on here can first author this too!
+ - Jay: Clean, add context, reorganize, executive summary, and solicit for feedback.
\ No newline at end of file