Differences between revisions 1 and 2
Revision 1 as of 2008-06-26 12:26:15
Size: 2990
Editor: kfc
Comment: Created by the PackagePages action.
Revision 2 as of 2010-03-17 13:13:02
Size: 2990
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 19: Line 19:
See ["TaskC.1AnalysisDocumentDetails#AccessLog"] See [[TaskC.1AnalysisDocumentDetails#AccessLog]]

Analysis of the Meta Data Manager GUI

  • What we have: Java-application with raw XML display and editing
  • Easy level 2 (according to Mads): DOM-tree based editing and validation through standalone Java application
  • MKE: rdf-links, dom + schema interface.
  • See also: Xmetal for Java-applet based GUI
  • We agreed on: A Java applet with DOM-tree based editing and validation. We can assume that users will have an up to date installation of Java.
  • We've considered using Java Webstart for deployment of the meta data manager application.
  • We have planned using the Summa technology for the search functionality in the meta data manager.

When addressing this task, we should note the following TDR requirements:

  • Access log required: B5.2, C3.2, R36

See TaskC.1AnalysisDocumentDetails#AccessLog

Prerequisites and Assumptions

The estimation of this task is based on these notes, which also should be taken into consideration when implementing the task:

BAM: Mellemløsning m. Summa-søgning u. rettigheder

TE: Java GUI. Søgning gennem Summa uden rettigheder. Eksplicit redigering af referencer, rettigheder, datastreams. Strict DOM editering. Udskudt: Oprettelse, sletning og batch.

TSH: No comments.

MKE: GUI-krav: dom+skema int., rdf-links, summa søgning + special parallel summa index over alle objekter (også slettede), webstart

KFC: Editering af enkeltobjekters metadata, find objekter (parallelt summaindeks med adgang til alle objekter), rettigheder, referencesystem. Java webstart.

TaskE.1AnalysisDocument (last edited 2010-03-17 13:13:02 by localhost)