Matthew,

This was the topic of a recent discussion on the BIBFRAME list [1], 
although the design solution is still wanting. One of the problems is 
that the pattern "volume/issue/page" is not universal -- there are parts 
with volumes, volumes with parts, volumes with no issues, issues without 
volumes, supplements to volumes (that aren't really issues), etc. 
Somewhere (I believe related to CONSER) there is a database of serial 
patterns that could reveal the complexity of this question. For an 
answer, you need to clarify the use case. The MARC holdings format 
provides enough information to allow issue arrival predication software 
to work. Do you need that level of precision? Many metadata formats that 
address journals (I'm thinking BIBO, OpenURL, etc.) go with 
volume/issue/page and just punt on the more complex patterns. I don't 
know how often they run into problems with their limited view.

kc
[1] starting with 
http://listserv.loc.gov/cgi-bin/wa?A2=ind1507&L=bibframe&T=0&P=216

On 8/18/15 3:28 AM, PHILLIPS M.E. wrote:
> But what property should I use to declare the volume/issue/page
> numbering of the article within the journal? It will have to be a
> property of the article. I cannot immediately see any suitable property
> in RDA – and I need to at least identify one which is appropriate before
> I can create a set of more exact subproperties as you are suggesting below.

-- 
Karen Coyle
[log in to unmask] http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet/+1-510-984-3600