## The heading should have the form: "2008-01-21 Iteration 7 Status Meeting"

= 2008-10-09 Mjølner developer meeting =

## ADD LINK to the agenda here.
##  [:LINK_GOES_HERE:Agenda]


== Questions from Mjølner ==

 1. Oprettelse af ny post fra template (Tidligere omtalt som ’prototype’). Se vedlagt sekvensdiagram. -> SEE BELOW
 2.  Import af data (fra Horizon som eksempel). Se vedlagt sekvensdiagram. -> POSTPONED
 3.  Eksport af data (til Horizon som eksempel). Se vedlagt sekvensdiagram. -> POSTPONED
 4.  Upload af filer. Se vedlagt sekvensdiagram. -> SEE BELOW
 5.  Er det muligt at slette en Content Model som endnu ikke er ”Published”? Denne funktionalitet vil være nyttig i forbindelse med ”Oprettelse af ny post fra template”. -> JA
 6.  Status på fremskaffelse af eksempler på queries til fremsøgning af Subtype. -> TO BE DONE

We answered these as best we could. There were two issues of special interest

== New DOMS services ==

Mjølner would like the following services in DOMS. They are not adverse to building them themselves, but it will ease the development of the GUI a lot.

=== Creation of Data object From Template ===

A service that creates a new data object from a template.
 * in: the pid of the template
 * out: the pid of the new object

Automates the housekeeping when instantiating the templates.

=== Bitstorage wrapper ===

A service that uploads a file and populates a given File object.
 * in: the local url of a file, the pid of a existing file object
 * out: nothing, throws exceptions if things break

This method performs all the bitstorage negotiation itself, and hides it from the GUI.

=== RIsearch wrapper ===

There are a few advanced queries that will often be used. These should have their own interface.

Find templates for the given content model in this collection
 * in: pid of a content model, a list of pids of collections
 * out: a list of pids,titles of templates for this content model or a subtype belonging to all the specified collections.

=== Finding the specific content model ===

A service to find the specific content model of a data object. Now, they have a long list, and this is difficult parsable. This must stop.









== Multiple inheritance ==

Mjølner really doesn't like multiple inheritance. They would much rather we did not allow for it. This must be discussed. 

== AOD ==

Mjolner expects the user only to upload files on a shared drive. ABR suggested that a browser could be used to browse the drive, so that the URL could easily be pasted into a box in the gui. We need to decide on how we do this, at any rate.

Mjolner makes a file object with the gui, and then the object is populated on upload. This is nessesary, as there are subtypes of file objects, and somebody must decide which one to use.