The EAD is for import-export | Libraries [reloaded]
The beginning of the ticket made me pretty scared, inporta citing various existing XML editors. The note ends happily on a happier fall: use ICA-Atom description software archives, use the input fields and then export the software inventory EAD export format as it exists.
For my part, I would have started with that: it is forbidden to write the EAD in hand. The EAD is a very good exchange format between two bases archives to share inventory. But it is useless to make a native format.
To make it more understandable for librarians (well, librarians who read this blog) comparison: it's a bit like asking a cataloguer to write his instructions in ISO2709 inporta or MarcXML.
It is better to spend time out automatically inporta produce the EAD from another format, that the move to enter tags and attributes by hand. Manual entry, even with all the help striking a good paid software as XMetaL is profitable for an inventory - and again - not two.
Moreover, in June, the same author referred to the mechanical SOSIE, which goes in the direction that I love! (Damage to the problems of software updates that signals). Case studies and feedback
I have just been confronted with an archival inventory tool does not export EAD. All he knows is the CSV export: one line per side, with systematic repetition of information in each row.
Except for injection into another site - such as the European Archives Portal - the CSV is indigestible, and that is where it is practical to say: "provide me the EAD." At least we know what it is (if it is an archivist). inporta The EAD is somehow an exchange format between two platforms, one can export the other importing. inporta
The transition from CSV EAD is no problem other than scientific: it must make choices about encoding. The rest of the computer - and the computer, it is (if you can give them instructions they know understand).
In short, the conversion I used the techniques inporta already mentioned: mailing Excel -> Word for an ugly XML file, where each line is a node with the same repeating information (not grouping series, inporta sub-series, funds, etc.., as demanded by the ISAD (G) and EAD) If you ignore all of the mail, here's a little tutorial (someone else's) video. Word file that calls the values of Excel cells regulates inporta the values in XML tags XSL sheet which includes information, according to Muenchian method already mentioned inporta on another blog in another life. Here is the style sheet used
Once the machine oiled, the longer the "scientific" work (which must be intuitive enough to actually an archivist) inporta of treating specific: in the input file, what is a fund, sub-series, etc.. You must then adjust the style sheet to each data source with changes (some sources need a tree with three levels, others only one).
Strongly agree: EAD-XML native format is a heresy. Above all, it seriously jeopardizes the future with the expected changes to the linked data: we will not be able to transform the EAD directly RDF triples sufficiently rich and relevant. Contrary to initial expectations, the adoption of the EAD has resulted in a large formalism inporta (priority to respect a syntax) sometimes to the detriment of the quality of content. In addition, there are too many implicit and missing information in the EAD. The draft EAD scheme comes too late and will be a compromise between exploitation and human reading machines (not enough inporta semantics). The need for a conceptual model for the archives (as FRBR, FRAD ... for libraries) and a large emergency. Archivists or at least the "e-archivists" should also consider the notions inporta of data versus documents (cf. the work of "Pédauque," inporta Salaun, Bachimont, Crozat ...) for their finding.
@ Louis: thank you properly focus the debate. I was not concerned that the technical inporta aspects of the processing chain. In itself, the EAD has been designed for the online & rsquo
The beginning of the ticket made me pretty scared, inporta citing various existing XML editors. The note ends happily on a happier fall: use ICA-Atom description software archives, use the input fields and then export the software inventory EAD export format as it exists.
For my part, I would have started with that: it is forbidden to write the EAD in hand. The EAD is a very good exchange format between two bases archives to share inventory. But it is useless to make a native format.
To make it more understandable for librarians (well, librarians who read this blog) comparison: it's a bit like asking a cataloguer to write his instructions in ISO2709 inporta or MarcXML.
It is better to spend time out automatically inporta produce the EAD from another format, that the move to enter tags and attributes by hand. Manual entry, even with all the help striking a good paid software as XMetaL is profitable for an inventory - and again - not two.
Moreover, in June, the same author referred to the mechanical SOSIE, which goes in the direction that I love! (Damage to the problems of software updates that signals). Case studies and feedback
I have just been confronted with an archival inventory tool does not export EAD. All he knows is the CSV export: one line per side, with systematic repetition of information in each row.
Except for injection into another site - such as the European Archives Portal - the CSV is indigestible, and that is where it is practical to say: "provide me the EAD." At least we know what it is (if it is an archivist). inporta The EAD is somehow an exchange format between two platforms, one can export the other importing. inporta
The transition from CSV EAD is no problem other than scientific: it must make choices about encoding. The rest of the computer - and the computer, it is (if you can give them instructions they know understand).
In short, the conversion I used the techniques inporta already mentioned: mailing Excel -> Word for an ugly XML file, where each line is a node with the same repeating information (not grouping series, inporta sub-series, funds, etc.., as demanded by the ISAD (G) and EAD) If you ignore all of the mail, here's a little tutorial (someone else's) video. Word file that calls the values of Excel cells regulates inporta the values in XML tags XSL sheet which includes information, according to Muenchian method already mentioned inporta on another blog in another life. Here is the style sheet used
Once the machine oiled, the longer the "scientific" work (which must be intuitive enough to actually an archivist) inporta of treating specific: in the input file, what is a fund, sub-series, etc.. You must then adjust the style sheet to each data source with changes (some sources need a tree with three levels, others only one).
Strongly agree: EAD-XML native format is a heresy. Above all, it seriously jeopardizes the future with the expected changes to the linked data: we will not be able to transform the EAD directly RDF triples sufficiently rich and relevant. Contrary to initial expectations, the adoption of the EAD has resulted in a large formalism inporta (priority to respect a syntax) sometimes to the detriment of the quality of content. In addition, there are too many implicit and missing information in the EAD. The draft EAD scheme comes too late and will be a compromise between exploitation and human reading machines (not enough inporta semantics). The need for a conceptual model for the archives (as FRBR, FRAD ... for libraries) and a large emergency. Archivists or at least the "e-archivists" should also consider the notions inporta of data versus documents (cf. the work of "Pédauque," inporta Salaun, Bachimont, Crozat ...) for their finding.
@ Louis: thank you properly focus the debate. I was not concerned that the technical inporta aspects of the processing chain. In itself, the EAD has been designed for the online & rsquo
No comments:
Post a Comment