What XML serializations should we use for our collections? What candidates are there?
We want to let users produce HTML albums. We can definitely fix the HTML template. However, if we want to let users customize the HTML, where should we draw inspiration from? ![[WWW]](/www/moin/htdocs/classic/img/moin-www.png){kind=small}
Python Server pages? MovableType templates? Just via CSS I'm thinking about templating languages because we want to give people a lot of flexibility without their having to change the Python code that generates the album.
How to handle alternative interfaces (in general and within our WxPython framework)?
Metadata handling. Each source of data will have different type of metadata. Do we try to reconcile them? Handle them separately? We need to get our feet wet with the SemanticInteroperabilityProblem.
I like to think of ScholarsBox/AxesOfGeneralizability when pondering various directions to improve the ScholarsBox. Which axis to go in and when? (That is, sources, data types, services, and quality)
Handle the issue of creative derivatives of images (resizing, cropping, filtering, etc.). What functionality to allow? How to keep track of provenance? What user interfaces for provenance?
How to make it easy to incorporate new sources? To begin with, we've hand-customized adaptors for each source. This approach certainly will not scale. What generalizations are there to think about data sources. Definitely we will look at MitOki and ImsGlobal/DigitalRepositoriesSpec for guidance in this area as well as to the Ims
How will we handle DigitalAnnotations? Will DigitalAnnotations be first class objects in the system?
Is this a good time to look at building a ChandlerProject parcel to get some insight? Probably.
Here we are concentrating on images primarily. But once we start to mix data types, we will have to worry about how to keep track of them. Can we get help from DataFormatRegistries?
