We’ve had a ticket running on this for the past few days, where we’ve
sort of been talking at cross purposes, with me asking for
corresponding locale terms to be added, and Bruce quite reasonably
wondering why that would be necessary. This morning it clicked for me
why these terms are confusing. They’re in the wrong part of the
schema.
These two are defined in cs-terms.locators, but they should be in
variables. cs-terms.locators automatically shift to singular or plural
depending on the value supplied by the user to a citation, so there’s
no need to explicitly peg singular or plural in the term label there.
If these are instead set as variables, then page-range could return
the whole “page” field from the DB, and page-first could be a virtual
field that returns the first numeric element. I think that was
probably the original intention.
Bruce, would you like to do the honors?
We’ve had a ticket running on this for the past few days, where we’ve
sort of been talking at cross purposes, with me asking for
corresponding locale terms to be added, and Bruce quite reasonably
wondering why that would be necessary. This morning it clicked for me
why these terms are confusing. They’re in the wrong part of the
schema.
You mean my schema addition here was a bug?
These two are defined in cs-terms.locators, but they should be in
variables. cs-terms.locators automatically shift to singular or plural
depending on the value supplied by the user to a citation, so there’s
no need to explicitly peg singular or plural in the term label there.
If these are instead set as variables, then page-range could return
the whole “page” field from the DB, and page-first could be a virtual
field that returns the first numeric element.
Well, CSL doesn’t really care about “fields,” but that would be how it
would work in Zotero.
Bruce
We’ve had a ticket running on this for the past few days, where we’ve
sort of been talking at cross purposes, with me asking for
corresponding locale terms to be added, and Bruce quite reasonably
wondering why that would be necessary. This morning it clicked for me
why these terms are confusing. They’re in the wrong part of the
schema.
You mean my schema addition here was a bug?
Yes. Not that anyone would hold it against you! Checking the svn log
for the date of the change was a salutary reminder of the amount of
work that has gone into this over the past three years and more.
These two are defined in cs-terms.locators, but they should be in
variables. cs-terms.locators automatically shift to singular or plural
depending on the value supplied by the user to a citation, so there’s
no need to explicitly peg singular or plural in the term label there.
If these are instead set as variables, then page-range could return
the whole “page” field from the DB, and page-first could be a virtual
field that returns the first numeric element.
Well, CSL doesn’t really care about “fields,” but that would be how it
would work in Zotero.
True. It’s been done now. The list of remaining issues is getting
encouragingly short!
Frank