Hello DSpace community, I have made some progress on my BTE issues and now I got it working to split the authors correctly into several fields and also to convert the LaTeX encoded characters automatically while importing. I did this by creating two new beans.
But there is still one issue left: importing from a bibTeX file does not import the type of the publication correctly. In BibTeX the type is noted not in a field, but with an @ at the top of the record. I understand how to add field mappings in the bte config file, but as the type is not a normal field I do not understand how I can get that. Before I try to create an alternative BibtexDataLoader in order to implement the type detection there I would like to ask if anyone else already has done this or if anyone else has also this kind of problem. Thanks and best regards Oliver Am Freitag, 10. Juni 2016 16:13:26 UTC+2 schrieb Oliver Goldschmidt: > > Hi Claudia, > > thank you very much for your reply! > I know the config file for BTE, but I do not see how I can split the > BibTeX field for author into several dc.contributor.author fields in the > DSpace record. As far as I know I can only map a key from the bibtex file > to a key in the config file, which maps to a dc field (but it seems to me > that its always only one field). For example in the > bibTeXDataLoader-section in bte.xml: <entry key="author" value="authors" /> > maps to the outputMap, where I find this element: <entry value="authors" > key="dc.contributor.author" />. My interpreation is, that the value of the > author field is set into the field dc.contributor.author - but I can't see > if I can process the BibTeX field before putting it into the DSpace field > (and I guess that would be necessary to split off the author string to get > it into multiple DC attributes). > > About the latex encoded ü: if I understand you correctly, I will have no > choice and need to convert such characters before I import the record into > DSpace. I guess that's not very comfortable (as that means I need to check > every BibTeX record before importing), but okay... > > Thanks > Oliver > > Am Freitag, 10. Juni 2016 14:55:05 UTC+2 schrieb Claudia Jürgen: >> >> Hi Oliver, >> >> the config file for BTE is: >> >> https://github.com/DSpace/DSpace/blob/dspace-5.5/dspace/config/spring/api/bte.xml#L256 >> which does a simple mapping of fields and defines the data loader. >> >> As for the encoding this is a bit tricky as it depends on the packages >> and inputenc used in the LaTeX itself. >> The indirect way to input e.g. ü is >> {\"u} or \"u >> using \usepackage[german]{babel} ü might be written "u >> and with >> >> \usepackage[ansinew]{inputenc}(windows) you can enter them directly afaik. >> >> Hope this helps >> >> Claudia Jürgen >> >> >> >> >> Am 10.06.2016 um 12:23 schrieb Oliver Goldschmidt: >> >> Hello DSpacers, >> >> currently I'm experimenting a little bit with importing BibTeX files using >> BTE. If a BibTeX record has multiple authors, I see something like this in >> the author field in the BibTeX file: >> author = {Me Myself and Oliver Goldschmidt and Fritz M{\"u}ller} >> >> As far as I know this is absolutely conform to the BibTeX standard. But the >> BTE importer messes the imported record up and writes exactly that string >> into one dc.contributor.author field. It also does not convert the latex >> encoding properly. I would expect the importer to create a record with >> three dc.contributor.author fields. Before I start digging in the code >> trying to improve this bad behavior: can this get corrected by >> configuration? >> >> Best >> Oliver >> >> >> >> -- >> Claudia Juergen >> Eldorado >> >> Technische Universität Dortmund >> Universitätsbibliothek >> Vogelpothsweg 76 >> 44227 Dortmund >> >> Tel.: +49 231-755 40 43 >> Fax: +49 231-755 40 32claudia...@tu-dortmund.dewww.ub.tu-dortmund.de >> >> >> >> >> *Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie >> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für >> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender >> und vernichten Sie diese Mail. Vielen Dank. Unbeschadet der Korrespondenz >> per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, >> wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder >> durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen. >> Important note: The information included in this e-mail is confidential. It >> is solely intended for the recipient. If you are not the intended recipient >> of this e-mail please contact the sender and delete this message. Thank >> you. Without prejudice of e-mail correspondence, our statements are only >> legally binding when they are made in the conventional written form (with >> personal signature) or when such documents are sent by fax. * >> > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
