Re: [Refdb-users] Importing RisX into RefDB

[Markus H. <mar...@mh...>]

Hi,

Bruce D'Arcus writes:
 > Right.  This is what I had in mind; the DTD ought to help users know 
 > what kinds of data goes where, and in so doing create valid records.  
 > However you decide to do it (one DTD vs. two), any technical details 
 > (XSLT on import, for example) ought to be completely hidden from the 
 > user.  I think you've got the right idea though!
 > 

The technical stuff can easily be hidden from the user by providing a
simple input filter like there is for MARC or Pubmed data. This filter
would run the appropriate XSLT transformations.

 > If you do the two DTD approach, this does raise the question of MODS 
 > again (e.g. -- the longer term).  It might be a good idea to look 
 > closely at that before working on any additional DTD (and after 
 > solidifying risX proper).  I'm not sure what specific data structures 
 > ought to be added to RefDB to enable some of the features I'd like to 
 > see in a reference manager app, but my sense is that MODS and 
 > Kaspaliste (which uses PostgreSQL, and has tables for notes and links) 
 > are where to look.
 > 

I currently hesitate to switch to MODS as it is implemented as a
Schema, not a DTD. Not many tools support this yet, and I can only
hope and pray that my favourite tool (Emacs and PSGML) will do so
eventually. But I agree that we should sit down and analyze how common
MODS data could be mapped to RIS or risx. Family duties may prevent
this right now, but I hope I'll be able to carve out some time next
week.

regards,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de