Comments for mark e. phillips journal

Comment on Aubrey: Our content delivery/metadata management system. by vphill

vphill — Tue, 09 Mar 2010 17:33:22 +0000

From the beginning of the project we knew we weren’t going to be releasing the code for this one. Mainly because I know that we don’t have the resources to support this sort of thing. I would however be interested in groups interested in hosting collections with our framework in our infrastructure. I haven’t figured out much of the issues with that , but that’s the model I think we would go for.

Comment on Aubrey: Our content delivery/metadata management system. by Mike G.

Mike G. — Mon, 08 Mar 2010 14:20:09 +0000

Great to read more about UNT’s work, Mark. Out of curiosity, is Aubrey available under an open source license, or do you plan on making it available?

Comment on How we use BagIt to ingest and store digital objects. by Brian Kennison

Brian Kennison — Fri, 05 Mar 2010 19:06:54 +0000

Thanks for the info! I’ve got some things in place but have a lot to do. I buy into the ideas expressed by the CDL of “permanent objects and disposable systems” and I’ve been trying to get a outline of what this repository system would look like. Your posts are most helpful.

Comment on How we use BagIt to ingest and store digital objects. by vphill

vphill — Fri, 05 Mar 2010 18:04:47 +0000

Descriptive metadata is handled in our delivery platform, called Aubrey, I’ll do a few posts about that in the near future.

We version all metadata modifications to both the structure of the object (ordering of fileSets, adding labels to manifestations and fileSets, page numbers and such to a digital objects) as well as version all descriptive metadata edits. This is helpful to be able to roll back changes that shouldn’t have been made as well as figuring out what happened if something that wasn’t supposed to be shared publicly got shared. As we look at raising the quality of our metadata I think the ability to version all of it is one of the measures that plays into it.

new ACPs can be run at anytime (for example if we decide to encode at a higher bitrate for video or audio, change sizes or just screw up on the delivery formats) by placing an AIP in the 3.ToACP folder in the desired dropbox and running the makeACP.py script again, it would then just overwrite the copy in aubrey (taking care not to write over the descriptive metadata , filenaming conventions help with this)

Comment on How we use BagIt to ingest and store digital objects. by Brian Kennison

Brian Kennison — Fri, 05 Mar 2010 17:45:21 +0000

Yes that helps. It expalains how the archive handles versions, essentially another manifestation). When a new version is ingested, I guess a new ACP is generated and overwrites the old ACP. Do you keep versions of the descriptive metadata if it changes? How/When are the different namespaces used?

Comment on How we use BagIt to ingest and store digital objects. by vphill

vphill — Fri, 05 Mar 2010 16:45:57 +0000

Yes the Trac wiki isn’t very clear.

We view coda (our digital archive thingy) as a write once system. If there are changes that need to happen to an object, it really depends on what the change is. Here are some changes that don’t require re-ingest

* descriptive metadata editing
* re-ordering of fileSets (page in a book out of order)

If there is a change to a file (someone misspelled their name on an ETD) or a missing page from a book, then the process is to grab the AIP from coda (it becomes a DIP at that point but the structure is the same), change what is needed and then load it back into the ingest system. We have one more dropbox which is a dropbox that doesn’t assign a new identifier and is used for both legacy content ingest as well as adding new versions into the system. coda will just maintain two “versions” of this object if it is re-ingested.

Does that help?

Comment on How we use BagIt to ingest and store digital objects. by Brian Kennison

Brian Kennison — Fri, 05 Mar 2010 16:36:56 +0000

Mark – Thanks for this series of posts! I’ve been looking at your site and on your TRAC wiki but these posts are much clearer. Thanks for sharing your methods and processes.

I was wondering about how (and how often) editing takes place. If a change needs to be made is the AIP retrieved, edited, and re-submitted as a DIP? Does the ingest process look for objects that already have an id?

Comment on Pauls wedding in Edmond and Oklahoma City added to photodatabase by Amira

Amira — Sat, 09 May 2009 01:43:49 +0000

I’ve seen the photodatabase, you got fine lens on pictures! Thanks for sharing your ideas here.

Comment on getting to the airport by val

val — Sun, 20 Nov 2005 22:51:44 +0000

So have they offered you a job yet?

Comment on On the phone at 5 am by val

val — Thu, 17 Nov 2005 02:43:03 +0000

Actually I was thinking about that the last time I was at the airport at 6:30 am a couple of weeks ago. I didn’t even want to text msg anybody because I figured it was too early…I think the best you can hope for is to have friends in multiple time zones – and preferably early risers in time zones ahead of you. Or else…take a book.