Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

biblatex2xml 5.0: "Did not recognize type ..."

Nick Bart
2013-07-16
2013-08-03
  • Nick Bart
    Nick Bart
    2013-07-16

    biblatex2xml 5.0 generates "Did not recognize type ..." messages for a number of biblatex entry types that are valid according to the biblatex manual.

    • mvbook and mvcollection are entry types for multi-volume books and collections. They could be treated like normal books and collections, except that they cannot contain maintitle fields. In MODS, they could be distinguished from normal books/collections by using a <genre authority="marcgt">multivolume monograph</genre> element on the top level.

    • review is treated as an alias for @article by the biblatex standard styles.

    • artwork, audio, commentary, image, jurisdiction, legislation, legal, letter, movie, music, performance, software, standard, video are treated as aliases for @misc by the biblatex standard styles.

    There may well be arguments for treating any of the types from the last two groups in a more specific way when converting them to MODS, but a useful first step would be for biblatex2xml to start accepting all of them as aliases for @misc, resp. @article.

     
    Last edit: Nick Bart 2013-07-16
  • Nick Bart
    Nick Bart
    2013-08-03

    Update: A few more valid biblatex types not recognized by biblatex2xml are:

    suppbook (alias for inbook)

    suppcollection (alias for incollection)

    suppperiodical (alias for article)

    reference (alias for collection)

    inreference (alias for incollection)

    mvproceedings (multivolume monograph variant of proceedings)

    mvreference (alias for mvcollection)