Changes to fields and item types for Zotero 5.1

145791012
  • To clean up some loose ends, I've broken the mold in MLZ and will be introducing new fields and types in the next release, coming up within the next couple of weeks. The changes will go straight into the database schema. That will break database compatibility with official Zotero, but the new version will be fully sync-enabled, both for the new fields and types, and for multilingual field variants. Sync to an official Zotero client will (sort of) work as well.

    In the new version, upgrade migration and the jiggery-pokery needed to preserve and extend sync functionality are controlled by a small set of mapping tables. This has lightened things considerably, and I'm open to making further modifications to the schema before the release, if there are specific requests. As a magnet for feedback, I've churned out a set of item type/field tables for the current MLZ dev version with a little help (well, a lot of help) from aurimas' excellent CSL mapping plugin:

    http://fbennett.github.com/z2csl/typeMap.xml

    Looking forward to the next major Zotero cycle, the core developers might welcome a concrete set of migration and CSL mappings to use as a starting point. So if there is something high on your wish list, feel free to take a look at the tables and ask for changes; I'll be happy to stir in anything specific for which there is rough concensus.
  • @fbennett: sounds very promising. Wish you a good coding and I hope I can try out Multilingual Zotero (MLZ) in the next weeks, which may be able to solve some of the open wishes I have (CSL mapping, Sorting Bibliography by Reference Type, multiple bibliographies).
    Is this still the way to install MLZ?
    http://gsl-nagoya-u.net/http/pub/zotero-multilingual-overview.html#installation
    Will try it on a Firefox Portable Version.
  • edited January 14, 2013
    The project now has a home here: http://citationstylist.org/

    (Edit: Note that the client and styles will change significantly when the next version goes live. It's a speed bump on the road to stability, but a bump nonetheless.)
  • Frank - how willing/interested would you be in implementing most of the consensual (or mostly consensual) changes discussed here?
    https://github.com/ajlyon/zotero-bits/issues?state=open
    If so, I'd be willing to try to help you compile a list - any thoughts on what format would be most useful?
    Best,
    Sebastian
  • That would be great. One thing I might do to help smooth the process is to build the MLZ field tables with highlights on fields not found in official Zotero. That way, we could for easily tell at a glance whether a proposed field has been covered or not.

    It would be really good to get a condensed picture of the consensus on next-version field assignments. Apart from anything else, it help me avoid conflicts with my current back-of-the-envelope additions.

    Just a simple list of CSL types/varname pairs will be fine for a start. It would be good to have a proposed label for the Zotero UI for each one, too, as that may affect variable names in the Zotero DB.
  • At present, archival collections cannot be properly included in a bibliography. Several years ago, erazlogo suggested correcting this – and some other more complex citation issues – with the addition of an "archival collection" item type:
    http://forums.zotero.org/discussion/2981/styling-archival-material/

    Style requirements for "Manuscript collections" are provided by CMS 16th, 14.232-242, as well as the US National Archives (NARA) guide "Citing Records in the National Archives of the United States" (http://www.archives.gov/publications/general-info-leaflets/17-citing-records.pdf).

    In brief, what is needed according to CMS is
    - name of author of the material collected or name of the group of documents
    - title of a specific item (if required)
    - name of collection
    - name of series
    - name of depository (archive)
    - place (location of depository)
    - URL

    To this I would suggest adding:

    - date range covered by the material (hopefully Z3.1 will be able to handle date ranges!)

    NARA has more detailed hierarchies, including file numbers and microfilm numbers, etc.

    Here are examples provided by CMS:
    14.241 Examples of bibliography entries for manuscript collections

    The style of the first six examples below is appropriate if more than one item from a collection is cited in the text or notes. In the second and third examples, commas are added after the initials to avoid misreading. See also 14.233.

    Egmont Manuscripts. Phillipps Collection. University of Georgia Library.
    House, Edward M., Papers. Yale University Library.
    Merriam, Charles E., Papers. University of Chicago Library.
    Pennsylvania Society for the Abolition of Slavery. Papers. Historical Society of Pennsylvania, Philadelphia.
    Strother, French, and Edward Lowry. Undated correspondence. Herbert Hoover Presidential Library, West Branch, IA.
    Women’s Organization for National Prohibition Reform. Papers. Alice Belin du Pont files, Pierre S. du Pont Papers. Eleutherian Mills Historical Library, Wilmington, DE.

    If only one item from a collection has been mentioned in text or in a note and is considered important enough to include in a bibliography, the entry will begin with the item.

    Dinkel, Joseph. Description of Louis Agassiz written at the request of Elizabeth Cary Agassiz. Agassiz Papers. Houghton Library, Harvard University.
    Note especially that quotation marks are not used for generic names in citing archival documents – something which cannot be achieved using the current Document or Manuscript item types.

    Also, the previous discussion linked above raised the issues surrounding listing archival collections in a separate section of the bibliography. A longer time line in resolving this more complex issue should not preclude at least being able to correctly list archival collections in the first place.

    ap
  • https://github.com/ajlyon/zotero-bits/issues/27
    I'd say this is pretty likely to get included.
    Neither field updates nor date ranges will make it into 3.1, which will be released on or before April 2nd, but Dan seemed optimistic about having a beta for 4.0 (with field updates) out pretty quickly after the 3.1 release, though it's going to be in beta for a while. Just to reiterate, this is not because field upgrades aren't considered a priority, but because they require major and potentially quite disruptive changes in the sync architecture (much of which is in place now).
  • Please add these item type labels

    -Working paper
    -White paper
    -Newsletter article

    Thanks.
  • Please read the first post on the first page of this thread.
    Use report for Working Paper and White Paper.
    How to cite a newsletter article depends on how it's published, but I doubt it can't be accommodated by one of the existing item types.
  • Thanks for the lead adamsmith! I think I understand why you're handling the item type labels the way you are (to fit with citation systems). I suppose I'll use tags to do any additional categorization. Tx.
  • What about item type "White Paper"
    Those paper that are available around the web not published or drafts of something published. IMO don't fit any of the existing types...

    Any idea?
    Thnks
    Luis
  • @luis: Quoting adamsmith above:
    Please read the first post on the first page of this thread.
    Use report for Working Paper and White Paper.
  • edited March 19, 2013
    Thanks Gracile :)
    If Report is a general thing, then I wonder why not to use just "Document" instead.
    Is there any "dictionary" which explains what each type refers to?
    The link there which leads to a whiteboard seems not to be that although new proposed types are somehow explained.

    In that comment it is mentioned that "remember that item types in Zotero are best understood as a set of fields and a set of ways they tend to be styled"
    IMO that is a view limited by the "designer" instead of by the user.
    If the user (or agreed version) sees "Whitepaper" different from "Working paper" then I would provide both entries, if the fact is that Zotero uses the same fields-template for both is an internal thing. This is both, easier to understand for a user, and scalable (and transparent) if in the future they split.

    Thanks again.
  • (For white papers of government, Multilingual Zotero (MLZ) adds a "Jurisdiction" field to its Report type.)
  • it's not just a problem of citation styles - though that's certainly a concern. It's also about export/data exchange, it's about keeping item types to a reasonable number simply to keep things manageable etc.

    We have talked about creating some instructions with more on item types and what to use them for. That needs to happen, but doing it well is a ton of work.
  • edited March 28, 2013
    The British Universities Film & Video Council has published guidelines for quoting films, tv shows and other of audio-visual content.

    In my opinion these recommendations are a bit over the top; from my experience in film studies you rarely see filmographies which are so fine grained (for example, most of the time, you don't give type or duration which are both mandatory here). But I guess these guidelines are quite useful as an orientation. Once Zotero is able to implement these guidelines, most situations/styles should be covered for audio-visual material.

    Here are the different types, the elements in italics are mandatory (for explanations of the element see the guidelines)

    Film:
    Given Title or ‘Clip Title’, Film Title [type, format] Production credit. Production Company/Sponsor/Private, Country of production, year of release. Duration. Start-end timings of extract. [release information, e.g. production company, catalogue number, date of specific edition] or point of access, e.g. archive collection, archive reference, or name of private collection, or original web URL (date of access).

    Television:
    Given Title or ‘Episode/Clip Title’, Main Programme/Series Title, Series No. [type, format] Production credit. ] Production Company/Sponsor/Private, Country of production, transmission time if known, transmission date, transmission channel. Duration. Start-end timings of extract. [release information, e.g. production company, catalogue number, date of specific edition] or point of access if applicable, e.g. archive collection, archive reference, or name of private collection, or original web URL (date of access).

    Radio:
    Given Title or ‘Episode/Clip Title’, Main Programme/Series Title [type, format] Production credit. ] Production Company/Sponsor/Private, Country of production, transmission time if known, transmission date, transmission channel. Duration. Start-end timings of extract. [release information, e.g. production company, catalogue number, date of specific edition] or point of access, e.g. archive collection, archive reference, or name of private collection, or original web URL (date of access).

    Other audio:
    Given Title or ‘Track title’, Main Title [type, format] Production credit. Production Company/Sponsor/Private, Country of production, date of recording if known. Duration. Start-end timings of extract. [release information, e.g. production company, catalogue number, date of specific edition] or point of access, e.g. archive collection, archive reference, or name of private collection, or original web URL (date of access).

    New media:
    Given Title or ‘Track title’, Main Title [type, format] Production credit. Production Company/ Sponsor/Private, Country of production, date created/uploaded/published. Duration. Start-end timings of extract. [release information, e.g. production company, catalogue number, date of specific edition] or point of access, e.g. original web URL (date of access).
  • edited March 29, 2013
    For using introduction, afterwords, preface and so on, I use Edition field with a customized style. Of course, I have problems with edition number (Chicago style adds "ed." after the edition variable, so I obtain "Introduction by John Doe ed.").
    A solution would be a new field. In Edition field I would put only edition number, in this new field I would write all foreword/introductions/preface/afterword: "Introduction by John Doe". Even if John Doe won't be in the fields of authors, the citation and bibliography will be perfect.
  • Might be appropriate to change the title of this thread to 4.1+
  • Could we DROP fields that we never use ? Would'nt that reduce the files size ? For instance, I don't care for language or location in library.

    And couldn't we rename a field ? I would need a field that shows my evaluation for the publication, though this can also be done by a tag.
  • edited October 8, 2013
    Both of these are display rather than database issue, so they're a different story from the rest of this thread (though dropping fields wouldn't empty file size in a noticeable way, no).
    We're quite interested in improving/cleaning up the display, so that might happen, though not super soon. It will likely take the form of moving unused fields to the bottom or so.
  • Moving unused fields to the bottom would be a great idea.
  • I am very excited that ArchivalCollection Type (https://github.com/ajlyon/zotero-bits/wiki/ArchivalCollectionType) is a proposed development for the new version of Zotero. I am a librarian at a special collections library, and I want to encourage the use of Zotero among my patrons (mostly historian). This development would make Zotero much more powerful for historical research.

    One question: Would it be possible to add a field for folder number? Many of our collections have thousands of folders.

    Thank you very much.
    Amanda
  • edited November 19, 2013
    the idea is to use "Loc. in Archive" for the location of an item in an archive - since these descriptions vary quite a bit - especially once you take into account international archives - I don't think it makes sense to try to include specific organizational sub-categories

    edit: oh sorry Amanda, I realize you know this already. So why folder and not, e.g. "box"? etc?
  • Hi Sebastian -

    Now that you say this, I do know this already! I'm sorry, I forgot. The reason I was excited about the folder level was that our finding aids have a new feature: component level IDs. You can pull the metadata from the finding aid at the folder level and then re-purpose it. I thought of Zotero. I'll investigate to see if this also works at the box level.

    In all honesty, it's probably best if the researcher can capture both the box and the folder number. The more information the better in terms of allowing future researchers to trace back to the document. The "Loc. in Archive" field is good for this - I'll just have to remind folks to use it for this purpose. Is there any possibility that it could be called "Loc. in Collection?" That might be more transparent.
  • Is there any possibility that it could be called "Loc. in Collection?" That might be more transparent.
    I think that makes sense once we add an archival collection field - which I'm pretty sure we will.
    Right now the status of collections within a larger archives is really quite awkward - you either treat each of the collections as a separate archive (i.e. enter them into the archive field) or you treat the collection as part of the Loc. in Archive (i.e. include them into to Loc. in Archive field) - in either case "Loc. in Collection" doesn't make much sense
  • One other question: Is there an estimated time frame for when the enhancements specific to archival collections will be released?
  • not really. Likely some time next year ;)
  • Is there according to anyone an item type one can use for citing a specific production and performance of for instance a theatre play, music performance and the like? Non of the item types that are there now have fields that cover what I need to put in it seems to me. For instance a theatre play performance would need Author, Play, Date of Play published, scriptwriter, director, performer(s), but also venue, and date of performance. There is no item type that can accommmodate multiple dates and data about both publication and performance of a work. Or am I missing something?
  • not currently. Event is probably your best workaround.
    A live performance item type is almost certainly going to be added:
    https://github.com/ajlyon/zotero-bits/issues/55
Sign In or Register to comment.