*Thread Reply:* You can change your time zone at the top of the grid
*Thread Reply:* I blocked out times that won’t work for me, but I may be able to be more flexible on those days if we can’t find anything else that works for everyone.
*Thread Reply:* how is there not a single hour we are all available 😂
*Thread Reply:* the best days are Thursdays Feb 17 and 24th at 1PM London time. Would you be willing to meet at 7AM (CDMX time) either of those days, @Miriam Bravo? If not, I could be free on Friday Feb 18th.
*Thread Reply:* Can we do feb 17 then? Something popped up on the 24th for me
Hi, @channel! We are meeting this Thursday at 13:00 London time in the SPAAM gather.town
Prior to the meeting, it would be great if everyone could identify which MIxS fields they think are specific to pathogen/microbial aDNA. I made a MInAS-pathogen google sheet for us to share our thoughts. I’ve gone through the MIxS tab and indicated my proposed assignments with some justifications. Please add yours to the same cells (but be careful not to delete anyone else’s text).
Looking forward to discussing metadata with you all!
*Thread Reply:* Thanks Kelly! By “specific to microbial/pathogen aDNA”, do you mean that the requirement category (M, C, etc..) might be different from other types of aDNA data? Or that the definition of the field might be different (maybe a question for @James Fellows Yates actually)? Also, should we also go through the environmental packages already or do we do that during/after the meeting?
*Thread Reply:* Yes, correct. You guys only do it for pathogens. Some fields might not be applicable in pathogens for human DNA for example.
But we will infer the common ones in later meetings
*Thread Reply:* I filled it out as if I were only thinking about pathogens. Some of the fields I said were mandatory/conditionally mandatory for pathogens could also apply to aDNA in general, but, like James said, I figured we would deal with the overlap in the wider metadata standards group.
*Thread Reply:* If you have time, go through the env packages. That way we can discuss everyone’s thoughts during the meeting. Since the whole group is meeting pretty soon (March 4th), we should try to talk about them at this meeting.
