Rebecca Bearden
My feedback
15 results found
-
42 votesRebecca Bearden
supported this idea
·
-
55 votesRebecca Bearden
supported this idea
·
-
13 votesRebecca Bearden
supported this idea
·
-
14 votesRebecca Bearden
supported this idea
·
-
9 votesRebecca Bearden
supported this idea
·
-
13 votesRebecca Bearden
supported this idea
·
-
13 votesRebecca Bearden
supported this idea
·
-
51 votesRebecca Bearden
supported this idea
·
-
47 votesRebecca Bearden
supported this idea
·
An error occurred while saving the comment -
418 votesRebecca Bearden
supported this idea
·
-
99 votesRebecca Bearden
supported this idea
·
-
78 votesRebecca Bearden
supported this idea
·
-
22 votesRebecca Bearden
supported this idea
·
-
164 votesRebecca Bearden
supported this idea
·
-
8 votesRebecca Bearden
supported this idea
·
I have had some luck with getting the fall/autumn season to start by utilizing the subfield x and y. Example: $$a v. $$b no. $$u 2 $$v c $$i (year) $$j (season) $$w f $$x 23 $$y ps23,21 $$8 1 for a publication issued Fall, then spring the following year. I will note that you also need to be careful what you input as your issue date. You may have to be more generous or conservative with that date for it to choose the proper year for each issue. However, the season prediction pattern problems I run into that are still problematic are 1. preferring Fall over Autumn in general. It would be nice if there were a way to specify which is preferred for a particular publication rather than editing manually, and 2. Whether winter is the final issue of the year, or the first issue of the year. It typically defaults as the first, and creates incorrect patterns depending on which year you want that issue to reflect vs. the others in that volume.