case history

OK, now that I’ve got a Bluebook style closer to working with Zotero,
I’m wondering how we should deal with case history.

Typically, this is just a field; a simple string. But it’s actually used
to indicate cited references of sorts.

Here’s the example I’m using from the Bluebook:

aff'd, 483 F.2d 754 (3d Cir. 1973), aff'd, 419 U.S. 345 (1974)

So note, here, it’s a structured record, within internal formatting.
It’s pointing to two subsequent decisions that affirmed the original
decision.

I don’t imagine lawyers much obsess about this because their styles tend
to be really consistent, but I’m not sure it’s smart for either CSL or
implementations to treat them as a simple string variable.

Any thoughts on dealing with this?

Bruce

Hi Bruce–

I’m delighted that you again have more time to work on CSL, despite
the grading and the manuscript preparation.

Perhaps we could resolve book editions citation before moving on
cases, especially since it has been discussed and Julian already has
a patch for it? It would be nice to incorporate that into Chicago
styles sooner rather than later.

In Zotero hierarchical types, whenever that’s done, case history
could be constructed via relationships, with “483 F.2d 754 (3d Cir.
1973)” as the short citation for the related case. It would even be
easier if subsequent citation format for cases was the same as above,
or could just be a different macro. I don’t know if anything can be
done on this until the hierarchical version is public though.

Best,
Elena

Elena Razlogova wrote:

I’m delighted that you again have more time to work on CSL, despite
the grading and the manuscript preparation.

Well I didn’t say that :wink:

Am just really noting the issue while it’s fresh in mind to resolve
"soon" and wondering if others have the time to think on the details in
the meantime.

Perhaps we could resolve book editions citation before moving on
cases, especially since it has been discussed and Julian already has
a patch for it? It would be nice to incorporate that into Chicago
styles sooner rather than later.

I see all three of these issues (types, editions, and history) as “need
to be resolved soon” (e.g. we can’t call 1.0 of CSL done until we do).
If we don’t solve this, we can’t support ANY legal citation. But none of
them are simple unfortunately.

Reminds me: I need to update the TODO.

Bruce

Elena Razlogova wrote:

In Zotero hierarchical types, whenever that’s done, case history
could be constructed via relationships, with “483 F.2d 754 (3d Cir.
1973)” as the short citation for the related case. It would even be
easier if subsequent citation format for cases was the same as above,
or could just be a different macro. I don’t know if anything can be
done on this until the hierarchical version is public though.

Here’s an idea that came to me:

  1. map a plain literal “history” to the “note” text variable. Zotero
    should do this now.

  2. the more relational solution is:

a. define “related*” variables.

 related-title
 related-date
 relation
 [problem is this list can get long b/c of flat model]

b. define a relation conditional attribute; something like:

It’s fairly simple and general, and I don’t see any other obvious way to
do this.

Bruce

Elena Razlogova wrote:

In Zotero hierarchical types, whenever that’s done, case history
could be constructed via relationships, with “483 F.2d 754 (3d Cir.
1973)” as the short citation for the related case. It would even be
easier if subsequent citation format for cases was the same as above,
or could just be a different macro. I don’t know if anything can be
done on this until the hierarchical version is public though.

Here’s an idea that came to me:

  1. map a plain literal “history” to the “note” text variable. Zotero

note is currently mapped to “extra” in zotero.
elena

should do this now.

  1. the more relational solution is:

a. define “related*” variables.

 related-title
 related-date
 relation
 [problem is this list can get long b/c of flat model]

b. define a relation conditional attribute; something like:

It’s fairly simple and general, and I don’t see any other obvious
way to
do this.

this should work fine, in theory.
elena

Elena Razlogova wrote:> On Dec 14, 2007, at 9:31 AM, Bruce D’Arcus wrote:

Elena Razlogova wrote:

In Zotero hierarchical types, whenever that’s done, case history
could be constructed via relationships, with “483 F.2d 754 (3d Cir.
1973)” as the short citation for the related case. It would even be
easier if subsequent citation format for cases was the same as above,
or could just be a different macro. I don’t know if anything can be
done on this until the hierarchical version is public though.
Here’s an idea that came to me:

  1. map a plain literal “history” to the “note” text variable. Zotero

note is currently mapped to “extra” in zotero.
elena

A legal citation isn’t complete without the history, so they need to
find something to map it to.

Bruce

  1. map a plain literal “history” to the “note” text variable. Zotero

note is currently mapped to “extra” in zotero.
elena

A legal citation isn’t complete without the history, so they need to
find something to map it to.

I mapped “history” to “genre” temporarily, until hierarchical
relationships are done–it will work for all legal item types.
“Genre” seems to function as a catch-all short description field
already for other types so seems logical.

Elena> Bruce

Elena Razlogova wrote:

  1. map a plain literal “history” to the “note” text variable. Zotero
    note is currently mapped to “extra” in zotero.
    elena
    A legal citation isn’t complete without the history, so they need to
    find something to map it to.

I mapped “history” to “genre” temporarily, until hierarchical
relationships are done–it will work for all legal item types.
“Genre” seems to function as a catch-all short description field
already for other types so seems logical.

I’d think of “genre” as almost a synonym for type: a natural language
description of what the item is.

History is a description of critical related resources.

E.g. they’re completely different.

Bruce

I’d think of “genre” as almost a synonym for type: a natural language
description of what the item is.

History is a description of critical related resources.

E.g. they’re completely different.

Feel free to create a new variable “history” in CSL then, and I’ll
map Zotero “history” to that variable.
Best,
Elena> Bruce

Bruce–

I’d think of “genre” as almost a synonym for type: a natural language
description of what the item is.

History is a description of critical related resources.

E.g. they’re completely different.

I unmapped “history” per your request. Simon can decide whether to
map “note” to “history” instead of “extra” – since he made that
change, it’s up to him to decide.

Best,
Elena> Bruce

Elena Razlogova wrote:

I’d think of “genre” as almost a synonym for type: a natural language
description of what the item is.

History is a description of critical related resources.

E.g. they’re completely different.

Feel free to create a new variable “history” in CSL then, and I’ll
map Zotero “history” to that variable.

OK:

$ svn commit -m “added ‘references’ variable to support case histories”

I was looking for a generic variable that would still work for case
histories, and this was the best I could come up with. Unless anyone has
any better ideas, let’s go with this then.

Thanks,
Bruce

OK:

$ svn commit -m “added ‘references’ variable to support case
histories”

I was looking for a generic variable that would still work for case
histories, and this was the best I could come up with. Unless
anyone has
any better ideas, let’s go with this then.

ok, “history” is now mapped to "references."
elena> Thanks,