Upgrade Storageposition v. jurisdiction v. type: in what order to minimize redundancy?
This is something I will eventually learn by trial-and-error but something I'd really like to learn without trial-and-error.
I think a citation schema comes down to breaking down each reference by its position, jurisdiction and type. In terms of writing codes, what order of assessing these three fields results in the least redundancy? I see different approaches in different styles in the repository, and can't quite figure out which approach is most efficient.
I think a citation schema comes down to breaking down each reference by its position, jurisdiction and type. In terms of writing codes, what order of assessing these three fields results in the least redundancy? I see different approaches in different styles in the repository, and can't quite figure out which approach is most efficient.
-
adamsmithI don't think it's possible to answer this generically. I'd typically test for position first - as most style do. Since many items don't have a jurisdiction, I'd tend to test for type first, but that really depends on the specifics.
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.