I am pretty new to EAD. However I have worked with other xml schemas
and found that at times it was helpful to have an editor that allowed a
"grid" view where the columns of data could be viewed like a table.
This allowed me to cut and past tabular data into the xml in one swoop
rather than having to do each one individually. It might be helpful to
talk about working with tabular data, and tools for migrating data into
Creighton Barrett wrote:
[log in to unmask]"
On 6 May 2010 12:13, Michele R Combs <[log in to unmask]> wrote:
I'm going to be teaching a one-day workshop on EAD encoding this summer and
am debating with myself whether it's better to use a full-featured XML
editor like oXygen, or go with something like NoteTab Pro or Notepad++ that
just provides some general (mostly visual) XML assistance. I've used
Notepad++ in the past with students in our LIS classes with pretty good
success. I can think of fairly obvious pros and cons for both approaches.
I'd appreciate your thoughts, particularly from anyone who has taught
I've never taught a workshop like this, but I did train some interns on EAD
this past year and my experience was that they all preferred oXygen over
NoteTab. I started one intern on NoteTab and when she started using oXygen
in a text-design course, she came back to the archives baffled about why I
would prefer NoteTab over oXygen. When you're not used to the hierarchical
structure of the code and how to detect the errors on your own in NoteTab
and a web browser, the error-highlighting features of oXygen become very
oXygen, of course, also has features that might make it easier to refer to
different things when you're talking to a large group, like color-coded code
and collapsible sections. And it transforms... If you're teaching
students, there is a pretty good student rate to purchase a license if they
want to pursue things further.
Just a few thoughts!
Halifax, Nova Scotia