new property for nonsort character count

[ntra00]

Consider adding a literal for the count of characters to ignore when sorting on another field, for example on a Title resource:

• mainTitle "The quick brown fox"
• nonSortNum "4"

This would mirror functionality of @Ind2 in MARC, and help going back to MARC.
The bflc:titleSortKey does exist: https://id.loc.gov/ontologies/bflc/titleSortKey
but it has not been widely used and repeats almost the entire field.

[jodiw01]

Definition: "Number of characters at the start of a label that should be skipped for indexing and sorting."

[NancyL]

Yes!

[kirkhess]

One thought I had was with a title resource like this:

        <bf:title>
            <bf:Title>
                <bf:mainTitle>Hainan hai yang yu ju yu fa</bf:mainTitle>
                <bf:mainTitle xml:lang="zh-hani">海南海洋渔具渔法</bf:mainTitle>
                <_:nonSortNum>4</_:nonSortNum>
            </bf:Title>
        </bf:title>

If you had 'nonSortNum' in a resource with more than one mainTitle which mainTitle is it for?
Maybe 9 datatypes you could apply to mainTitles would be more specific?

[kirkhess]

you also could define a list like notetype for ind1 and ind2 - then you could apply this in a lot of similar situations and it wouldn't be title-specific.

<bf:mainTitle rdf:datatype="http://id.loc.gov/vocabulary/indicator_2/4">The quick brown fox</bf:mainTitle>

[kefo]

Not a fan of the datatype idea. That's not to say I have a good/better solution (but this sentence isn't an endorsement either).

[NancyL]

Okay, so when we developed this, we weren't modeling script/transliteration this way, and I guess we need to move there. For LC, I would suppose you could specify that it goes with the :mainTitle that doesn't have a language tag???

[NancyL]

In Sinopia, we will still have them in 2 separate title nodes, since we cannot at this time repeat properties in this way.

[kirkhess]

I think this new transiteration model is better because the literals are joined and the pattern works for any transliterations like provision activities and editions w/o a special class.

Maybe there's no good solutions for legacy concepts like the 245 ind2 so maybe a marc key is better?

[NancyL]

I don't disagree with the model, just we can't do it just now in Sinopia. And I see with it there could even be 2 separate non-filing indicators.

the titleSortKey seems like it would have the same problem...

[jodiw01]

nonSortNum will be added to the BFLC ontology

[NancyL]

So instead of having 2bf:maint Tiles in a node, can’t we make 2 nodes? That way you can have other parts of the title bound together rather than mixes

…

Sent from my iPhone On Oct 4, 2022, at 6:09 PM, Jodi Williamschen ***@***.***> wrote:  Closed #96<#96> as completed. — Reply to this email directly, view it on GitHub<#96 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGXZNXT7OHQMP4DFQVB7C3WBRCBBANCNFSM6AAAAAAQWY6SU4>. You are receiving this because you commented.Message ID: ***@***.***>

[ntra00]

yes, it's fine to have two Titles with only one mainTitle each.