I think Dan in his statement above where he writes
"If one wanted to put a part named "Index" at the end of all the volumes (v. 1, v. 2, etc.), then one would need to give explicit numbers to all volumes, and give the index a higher number. So this use case devolves into my original implementation, after a bit more work by the user.
Another use case. Say I want to put "Introduction to the Collection" before the numbered volumes. This one is easier: I'd only have to give the Introduction a number -- any number -- and it will display before the (null) volumes. This is equivalent to the work required in my original implementation, where the user would put, say, -1 as the sort number, which would be displayed before the default 0's."
You could have say 3 parts
v.1
v.2
v.3
Index
you then have a column in the table specifying sort order.
part sort order
v.1 1
v.2 2
v.3 3
Index 4
if no order is applied in Dan's code you have the following where sort label would take over
I think Dan in his statement above where he writes
"If one wanted to put a part named "Index" at the end of all the volumes (v. 1, v. 2, etc.), then one would need to give explicit numbers to all volumes, and give the index a higher number. So this use case devolves into my original implementation, after a bit more work by the user.
Another use case. Say I want to put "Introduction to the Collection" before the numbered volumes. This one is easier: I'd only have to give the Introduction a number -- any number -- and it will display before the (null) volumes. This is equivalent to the work required in my original implementation, where the user would put, say, -1 as the sort number, which would be displayed before the default 0's."
You could have say 3 parts
v.1
v.2
v.3
Index
you then have a column in the table specifying sort order.
part sort order
v.1 1
v.2 2
v.3 3
Index 4
if no order is applied in Dan's code you have the following where sort label would take over
part sort order
v.1 0
v.2 0
v.3 0
Index 0