On Monday, April 8, 2019 at 2:53:59 PM UTC-4, David Bigwood wrote: > > Any suggestions for administrative data schema to use in DSpace, > resolution, date scanned, where scan was done.... >
That's a tough question for others to answer, because crafting a metadata plan is largely a guessing game, about what people will want to know in the future. But Google found me this: www.loc.gov/standards/mix/docs/NISODataDictionary_March2002.doc <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=6&ved=2ahUKEwiptuzci8PhAhUDWq0KHXjyAiMQFjAFegQIBRAC&url=http%3A%2F%2Fwww.loc.gov%2Fstandards%2Fmix%2Fdocs%2FNISODataDictionary_March2002.doc&usg=AOvVaw2pf5v9YXUeU5unMotVJ9jb> It might be a good starting point for thinking about what data you can resonably capture or extract, and what would be important to your organization for improving your process and organization, or guiding future equipment purchases. Some of those data you mention are not just administrative. Some users may want to narrow their searches to high (or low) resolution, for example. -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
