Skip to Content.
Sympa Menu

metadata-support - Re: [Metadata-Support] Best practice to test new metadata

Subject: InCommon metadata support

List archive

Re: [Metadata-Support] Best practice to test new metadata

Chronological Thread 
  • From: Ken Weiss <>
  • To: "" <>
  • Subject: Re: [Metadata-Support] Best practice to test new metadata
  • Date: Fri, 14 Feb 2014 21:33:58 +0000
  • Accept-language: en-US

Thanks, Tom. I will update our development SP to consume the preview


Ken Weiss

UC Office of the President 510-587-6311 (office)
California Digital Library 916-905-6933 (mobile)
UC Curation Center
415 20th Street, 4th Floor
Oakland, CA 94612

On 2/14/14 12:33 PM, "Tom Scavo"

>On Fri, Feb 14, 2014 at 12:05 PM,
> wrote:
>> I am clearly very confused about the intended purpose of the 'preview'
>> metadata aggregate. Rather than get into that now, though, I would like
>> find out what the best practice is to test changes to production
>When we roll out major changes to InCommon metadata, we will first
>deploy them to the preview aggregate before we move them to
>production. For example, we have plans to introduce a new schema, the
>MDRPI schema, and some new metadata elements that depend on that
>schema. These will be deployed to the preview aggregate first. After
>some reasonable amount of baking time, we will move those changes to
>production. In this way, problems associated with this new schema will
>be minimized. See this wiki page for more information about the three
>metadata aggregates:
>Hope this helps,

Archive powered by MHonArc 2.6.16.

Top of Page