# page-range, page-first

**URL:** <https://discourse.citationstyles.org/t/page-range-page-first/714>\
**Category:** CSL Development\
**Created:** [August 4, 2009, 10:47pm UTC](https://discourse.citationstyles.org/t/page-range-page-first/714 "2009-08-04T22:47:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Frank\_Bennett](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.citationstyles.org/frank_bennett/32/198_2.png) [@Frank\_Bennett](https://discourse.citationstyles.org/u/Frank_Bennett)\
**Post date:** [August 4, 2009, 10:47pm UTC](https://discourse.citationstyles.org/t/page-range-page-first/714/1 "2009-08-04T22:47:42Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Bruce\_D\_Arcus1](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bruce\_D\_Arcus1](https://discourse.citationstyles.org/u/Bruce_D_Arcus1)\
**Post date:** [August 5, 2009, 2:03am UTC](https://discourse.citationstyles.org/t/page-range-page-first/714/2 "2009-08-05T02:03:15Z")

</div>

> 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

---

<div class="post-metadata">

**Author:** ![Frank\_Bennett](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.citationstyles.org/frank_bennett/32/198_2.png) [@Frank\_Bennett](https://discourse.citationstyles.org/u/Frank_Bennett)\
**Post date:** [August 5, 2009, 2:32am UTC](https://discourse.citationstyles.org/t/page-range-page-first/714/3 "2009-08-05T02:32:43Z")

</div>

> > 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