| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
public:nnels:cataloguing:start:subjectheadings [2018/10/19 21:22]
robert.macgregor |
public:nnels:cataloguing:start:subjectheadings [2024/05/09 05:04] (current)
|
| ^ X̱wi7x̱wa Classification and Names | Nice to have for collections related to indigenous material | Has to be used in conjunction with other subject headings | | ^ X̱wi7x̱wa Classification and Names | Nice to have for collections related to indigenous material | Has to be used in conjunction with other subject headings | |
| |::: | | Likely require more work to implement | | |::: | | Likely require more work to implement | |
| | ^ THEMA | | | |
| | |::: | | | |
| | ^ Sears | | | |
| | |::: | | | |
| |
| Links to each: | Links to each: |
| |
| [[https://xwi7xwa.library.ubc.ca/collections/indigenous-knowledge-organization/subhead/ | X̱wi7x̱wa Classification and Names]] | [[https://xwi7xwa.library.ubc.ca/collections/indigenous-knowledge-organization/subhead/ | X̱wi7x̱wa Classification and Names]] |
| | |
| | Sears List of Subject Headings |
| |
| At a glance I like BISAC because it's small and simple. We could incorporate the whole scheme into Drupal, and it would be small enough that typing a bit of the heading would yield a usable drop-down selection. Of course not being able to copy catalogue means that we would have to spend a bit more time reading the description (unless we could find a place to copy from). Also it doesn't describe fiction very well - basically just Genre. It might be a scheme we could use for Non-fiction though - for example look at History; I think it would describe history books to a reasonable level - basically time and place. | At a glance I like BISAC because it's small and simple. We could incorporate the whole scheme into Drupal, and it would be small enough that typing a bit of the heading would yield a usable drop-down selection. Of course not being able to copy catalogue means that we would have to spend a bit more time reading the description (unless we could find a place to copy from). Also it doesn't describe fiction very well - basically just Genre. It might be a scheme we could use for Non-fiction though - for example look at History; I think it would describe history books to a reasonable level - basically time and place. |
| I also like BISAC, which is easy to navigate and use. CSH doesn't describe fiction well either. FAST is good because it renders results, but I think for it to work we'll have to set up criteria to pick and choose from what are there. Sometimes when I type in the field, a better term appears on the list.-- LL | I also like BISAC, which is easy to navigate and use. CSH doesn't describe fiction well either. FAST is good because it renders results, but I think for it to work we'll have to set up criteria to pick and choose from what are there. Sometimes when I type in the field, a better term appears on the list.-- LL |
| |
| Just went through THEMA - I like how it handles Non-Fiction (although it's still pretty unwieldy), however fiction is the sticking point again. It gives broad genres and leaves it at that. Describing the fiction items could be tough because if we aren't copying someone else's work (ie: OCLC) we need to figure out what's going on in the book by the jacket cover/description which takes time. Which brings up the question - does the fiction need to be that well described? Going back to BISAC it would describe a gay romance as FICTION / Romance / LGBT / Gay, which for most patrons browsing would probably be good enough to get them where they are going, at which point it's up to them to read the description, esp. if it has FICTION / Science Fiction / Time Travel attached to it as well. But if someone wants an historical fiction that takes place in France, that may be tough... - RM | Just went through THEMA - I like how it handles Non-Fiction (although it's still pretty unwieldy), however fiction is the sticking point again. It gives broad genres and leaves it at that. Describing the fiction items could be tough because if we aren't copying someone else's work (ie: OCLC) we need to figure out what's going on in the book by the jacket cover/description which takes time. Which brings up the question - does the fiction need to be that well described? Going back to BISAC it would describe a gay romance as FICTION / Romance / LGBT / Gay, which for most patrons browsing would probably be good enough to get them where they are going, at which point it's up to them to read the description, esp. if it has FICTION / Science Fiction / Time Travel attached to it as well. But if someone wants an historical fiction that takes place in 17th century Paris, that may be tough... - RM |
| | |
| | ===== Implementation questions ===== |
| | * NNELS relies on other library, publisher and distributor records for its metadata. The most common subject headings used in these records are probably LOC (from libraries) and BISAC (from publishers). If another subject classification were to be used, NNELS would need to implement a crosswalk/mapping from LOC and/or BISAC to this subject classification in order to automate the assignment of subject terms to records. Given this... |
| | * it might be easiest to utilize a subset of LOC subject headings for NNELS? we would map LOC subject headings to a smaller subset (similar to what we did for our genre taxonomy) |
| | * we could additionally develop a BISAC to LOC (for NNELS) crosswalk? |
| | * we could also map LOC to BISAC. Is there a crosswalk that already exists? |
| | |
| | ............................. |
| | |
| | If we go with a simplified version of LOC we could copy catalogue from libraries easily enough. How would we determine what the subset is? Do we just cap the depth of the subject heading at like 2 or 3 layers or something and lop off anything beyond that? |
| | |
| | I think regardless, it might be worthwhile putting one BISAC heading in. BISAC seems to use pretty natural language, and I assume the keyword searches might have an easy time hitting on one of the parts of a BISAC heading. I do think BISAC lacks the depth to be used alone, although the lack of depth also allows a heading to be picked from the list of terms and applied with relative ease. - RM |
| | |
| | I am not as familiar with the collection as I would have liked to be. From the record sets I have been working on, BISAC would be a good fit. - LL |
