Patrick: I can only ask: enough for what? If you haven't a solid idea of what you want the metadata to do, it's hard to evaluate either quantity or quality. Metadata is not static--if it's not regularly evaluated, improved and added to, it tends to lose its value and usefulness over time. Diane On Fri, Feb 10, 2012 at 4:27 PM, Ethan Gruber <[log in to unmask]> wrote: > An interface is only as useful as the metadata allows it to be, and the > metadata is only as useful as the interface built to take advantage of it. > > Ethan > > On Fri, Feb 10, 2012 at 4:10 PM, David Faler <[log in to unmask]> > wrote: > > > I think the answer is make sure you are able to add new elements to the > > store later, and keep around your source data and plan to be able to > > reprocess it. Something like what XC is doing. That way, you get to be > > agile at the beginning and just deal with what you *know* is absolutely > > needed, and add more when you can make a business case for it. > Especially > > if you are looking to deal with MARC or ONIX data. > > > > On Fri, Feb 10, 2012 at 3:57 PM, Patrick Berry <[log in to unmask]> wrote: > > > > > So, one question I forgot to toss out at the Ask Anything session is: > > > > > > When do you know you have enough metadata? > > > > > > "You'll know it when you have it," isn't the response I'm looking for. > > So, > > > I'm sure you're wondering what the context for this question is, and > > > honestly there is none. This is geared towards contentDM or DSpace or > > > Omeka or Millennium. I've seen groups not plan enough for collecting > > data > > > and I've seen groups that are have been planning so long they forgot > what > > > they were supposed to be collecting in the first place. > > > > > > So, I'll just throw that vague question out there and see who wants to > > take > > > a swing. > > > > > > Thanks, > > > Pat/@pberry > > > > > >