Hi all, we have had several emails/discussions with several groups now on metadata in KBase. Now a couple of people are talking about using the API to store metadata. There is a lot of prior discussion of metadata and metadata standards outside KBase and I think it is important to find a solution that integrates well with the external standards community. And in addition, rather than having a solution creep into place, I think it would be good to get in front of this and define what it is that we (as KBase) want. As a result I mentioned in a recent discussion the fact that we have an implementation of this in MG-RAST that might be worth looking at. As a punishment for this I was asked to put together a document outlining our solution for this in MG-RAST (see attached). There are some questions that I see us faced with: - do we need a single metadata strategy for KBase - what aspects of metadata are required for each domain - what type of solution are people comfortable with - what are our customers comfortable with I am sure I am missing tons of stuff that we need to think about and agree on a solution for, but hopefully this will be food for thought. Best, Folker