Project <daofind>

Questions

for the final discussion, May 28, 2005



The concept:

 

  • Should data entering / capturing tools be designed as distinct software units for a workbench approach?

Supported
 

  • Should there be a separate set of publishing tools (XSLT style sheets) available or integrated into the tool set?

Yes and there should be special style sheets for proof reading during the entering process.

  • Should entering / managing / publishing be conceived as far as possible in XML-format (file-system)? Were are the limits?

A start with file systems makes available all flexibility. Then databases might be integrated later as far as necessary.

  • Should we continue the plans to use open source software for editing and search facilities?

Supported

  • Should user interfaces be customizable (with templates)?

Supported

Linking between the three instances (for some simple examples):


  • What might be the problems with a strategy that uses pointers and xlink-elements in the xml-files and aims at a final combination with style sheets for presentation (esp. for the presentation of the holdings guide or for providing access to digital objects in online finding aids) ?

A rather simple start for a restricted problem in the form of an 80% solution may provide the opportunity to learn more and to see later how further expansion might be possible.

  • Would that be transferable in case of data exchange?

That is an open question for a further working agenda.

Perspectives outside: What is necessary for future integration into joint access points?


  • Should it be harvestable? Should it be reachable for federated search / meta search engines?

  • Should it be integratable into “union finding aids”

  • Is there a need for integrated presentation -

    • if style sheets are delivered together with the finding aids files?

    • or perhaps as a sort of lower level underneath a level of integrated presentation?

The data should be reachable for search engines. It depends on the architecture of the gateway, whether they are harvested, perhaps in form of a subset of elements, whether they are extracted or transmitted.
It might be interesting to think of a horizontal level above which an integrated presentation would be offered and under which finding aids are presented with their own style sheets.


What are the needs for a secure integration into the RLG-databases?


  • Are there any specific demands besides the best practice guidelines for EAD?

The best practice guidelines are the main orientation.

  • How are images treated in the moment?

Images are stored on the web-server of the delivering institutions.

  • Are there intentions to integrate EAC?

RLG thinks about integrating EAC.

Persistent identifiers


  • Should we use a Bundesarchiv wide syntax for creating file names for images?

An institution wide naming system is essential. But also management must be considered.

  • Would it be recommended to use the ID-attribute extensively?

It depends. For linking between the instances it seems to be useful.

Profiling


  • Should we formulate a special METS profile for our application?

First we will have a look at the existing profiles and see which one is nearest to our own expectations.

  • Should there be a similar profiling / documentation of the use of EAC and perhaps for EAD?

The best practice guidelines have a similar function.

Encoding analogues


  • for which other standards would it be useful to apply encoding analogues? For Germany ISAD(G), ISAAR (CPF), DC, OAI would be the mainly relevant standards.

There is no syntax for encoding analogues. However this function can easily be used for translation into a database.

Presentation


  • Are there any ideas for alternatives to navigation trees? Does some one know about experiments with graphic presentation of topic maps and / or svg-maps?

User studies say that navigation trees are not always understood. However there are some thoughts but no experiences with graphic alternatives.

Try out:


  • Should we already try to provide the ways for using German (or chooseable or customizable) tags sets ?

That would be supported. There are ideas about creating a formal apparatus to check the translated versions against the original DTD/schema to assure the functioning.

Are there any recommendations for the 3rd European Conference on EAD and EAC in 2006, hosted by the Bundesarchiv?

Interesting subjects might be: All aspects of interoperability, protocols for interchangeability, translation of tags etc. Workshops before and after, and two tracks for beginners and advanced implementers might be useful.


29.05.2005