Google Scholar Taxonomy vs. FAST for 'Subject' Metadata

[chrisdaaz]

Severity

Is the production site running?

• [x] yes
• [ ] no

Are staff blocked from performing their work?

• [ ] yes
• [x] no

Descriptive summary

I'm not sure if this is the appropriate place for questions/ discussions that may impact future development, but I'd be interested in thoughts about FAST Subject Headings vs. Google Scholar's Subject Taxonomy.

See the subject facets and subcategories for GS here: https://scholar.google.com/citations?view_op=top_venues&hl=en

vs.

FAST Subject Headings: http://fast.oclc.org/

My sense is that using GS subject taxonomy will make IR content more easily discoverable in GS, than using FAST. Thoughts?

Expected behavior

Make the Subject field in the upload form a controlled vocabulary selection.

Actual behavior

The field is free-text.

Related work

Related to #87

[davidschober]

I think this is a fine place for these discussions. It keeps a record, etc.

On Feb 9, 2017, at 10:29 AM, Chris Diaz notifications@github.com wrote:

Severity

Is the production site running?

yes no Are staff blocked from performing their work?

yes no Descriptive summary

I'm not sure if this is the appropriate place for questions/ discussions that may impact future development, but I'd be interested in thoughts about FAST Subject Headings vs. Google Scholar's Subject Taxonomy.

See the subject facets and subcategories for GS here: https://scholar.google.com/citations?view_op=top_venues&hl=en https://scholar.google.com/citations?view_op=top_venues&hl=en vs.

FAST Subject Headings: http://fast.oclc.org/ http://fast.oclc.org/ My sense is that using GS subject taxonomy will make IR content more easily discoverable in GS, than using FAST. Thoughts?

Expected behavior

Make the Subject field in the upload form a controlled vocabulary selection.

Actual behavior

The field is free-text.

Related work

Related to #87 https://github.com/nulib/institutional-repository/issues/87 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nulib/institutional-repository/issues/88, or mute the thread https://github.com/notifications/unsubscribe-auth/AElKnqFAN17uOmCNOX8EKvPZhDOFndwAks5raz7cgaJpZM4L8WM0.

[davidschober]

@csyversen @kdid to discuss.

[davidschober]

relates to #47

Note Durham has integrated fast Fast Integration in Sufia from Sufia Features int the wild

[csyversen]

I think this is a really good topic to bring up in one of the hydra slack channels. Most institutions would probably be interested in something like this, i bet. But i also don't really know much about this, so who would be the person to talk about it? @cpd3149 ?

[chrisdaaz]

i'm meeting with jen young about this later this month, but yeah i should talk to hydra slack too.

[csyversen]

that sounds like a good plan, meet with @jenyoung first and figure out what NU wants and then talk to the rest of the community. This might end up being a cool sufia feature we can push upstream

[chrisdaaz]

not really hearing much from hydra on this front, but there's docs for autocomplete in HYRAX using FAST https://github.com/projecthydra-labs/hyrax/wiki/Autocomplete-in-Hyrax

if i were to guess, the community is likely to stay away from controlled vocabularies that don't use URIs, like GS