search

ualbertalib / HydraNorth

This repo is deprecated. Succeeded by https://github.com/ualbertalib/jupiter. This codebase was a IR built based on Samvera/Sufia
11 stars 4 forks source link

ERA_Collections: Official collection of collections #76

Closed pbinkley closed 9 years ago

pbinkley commented 9 years ago

As admin I want to be able to select which collections are ‘official’ and displayed on the main ERA/repository ‘front door’, and to be able to refer to these collections with permanent ids Implement as new tab, pending Natasha's recommendation Admin can create communities and collections, and assign their nesting relationships Filter based on a flag for inclusion in public navigational structure (Note: will have to revisit when Hydra::Works comes out)

pbinkley commented 9 years ago

Question: will collections have ARKs? Existing handles are well used.

pbinkley commented 9 years ago

May depend on Hydra::Works.

weiweishi commented 9 years ago

Collection model in Sufia includes: Sufia::Noid. But no ARK yet.

pgwillia commented 9 years ago

note: FeaturedWorks is limited 5 and stored in a db table. Not exactly the model I want.

Want to be able to facet based on published => indexed in Solr

Propose

Won't do

pbinkley commented 9 years ago

This looks good. I think it would be good to use a different name than "featured": maybe "published". "Featured" suggests items selected out of the mass for special attention, whereas our feature is intended to give the full set of public collections that are part of the "official" HydraNorth navigation.

That would allow it to live alongside a "featured" collection feature in the narrow sense, too.

Peter

On 3 March 2015 at 12:23, pgwillia notifications@github.com wrote:

note: FeaturedWorks https://github.com/projecthydra/sufia/blob/master/sufia-models/app/models/featured_work.rb is limited 5 and stored in a db table. Not exactly the model I want.

Want to be able to facet based on featured => indexed in Solr

Propose

  • implementing collections#index route so that there is a target which enumerates collections
  • admin should be able to feature collection from collections#show
  • only featured collections appear in collections#index
  • admin should be able to un-feature collection from collections#index
  • add communities tab to homepage which links to collections#index
  • results should include share-with-me links

Won't do

— Reply to this email directly or view it on GitHub https://github.com/ualbertalib/HydraNorth/issues/76#issuecomment-77015131 .

pgwillia commented 9 years ago

How about curate and weed instead of publish/un-publish, feature/un-feature or official/unofficial?

pbinkley commented 9 years ago

hmm - curate could more precisely apply to a lot of things that we might ultimately want to do with collections (e.g. allow trusted user to manage an "official" collection, to give it intellectual authority). And we might want the "feature" feature (sigh) along side the official navigation structure.

The essence of it is to provide a navigational structure designed and maintained by ERA admin, in contrast to any user-created collections that might arise. But we know that ERA admin might also have collections that don't belong in this structure (but which might still be public, so the "publish" label might be confusing). Maybe "bless"/"unbless"?

Peter

On 3 March 2015 at 15:28, pgwillia notifications@github.com wrote:

How about curate and weed instead of publish/un-publish, feature/un-feature or official/unofficial?

— Reply to this email directly or view it on GitHub https://github.com/ualbertalib/HydraNorth/issues/76#issuecomment-77050808 .

gsharder commented 9 years ago

Official/unofficial makes sense to me -- my two cents.

On Tue, Mar 3, 2015 at 3:43 PM, Peter Binkley notifications@github.com wrote:

hmm - curate could more precisely apply to a lot of things that we might ultimately want to do with collections (e.g. allow trusted user to manage an "official" collection, to give it intellectual authority). And we might want the "feature" feature (sigh) along side the official navigation structure.

The essence of it is to provide a navigational structure designed and maintained by ERA admin, in contrast to any user-created collections that might arise. But we know that ERA admin might also have collections that don't belong in this structure (but which might still be public, so the "publish" label might be confusing). Maybe "bless"/"unbless"?

Peter

On 3 March 2015 at 15:28, pgwillia notifications@github.com wrote:

How about curate and weed instead of publish/un-publish, feature/un-feature or official/unofficial?

— Reply to this email directly or view it on GitHub < https://github.com/ualbertalib/HydraNorth/issues/76#issuecomment-77050808>

.

— Reply to this email directly or view it on GitHub https://github.com/ualbertalib/HydraNorth/issues/76#issuecomment-77054510 .

Geoff Harder Associate University Librarian Information Resources and Digital Initiatives

University of Alberta Libraries

2-10H Cameron Library, University of AlbertaEdmonton, AB, Canada T6G 2J8 780.492.7914 geoffrey.harder@ualberta.ca geoffrey.harder@ualberta.ca library.ualberta.ca http://library.ualberta.ca

sfarnel commented 9 years ago

I think official/unofficial is simple and clear.

On Tue, Mar 3, 2015 at 4:41 PM, gsharder notifications@github.com wrote:

Official/unofficial makes sense to me -- my two cents.

On Tue, Mar 3, 2015 at 3:43 PM, Peter Binkley notifications@github.com wrote:

hmm - curate could more precisely apply to a lot of things that we might ultimately want to do with collections (e.g. allow trusted user to manage an "official" collection, to give it intellectual authority). And we might want the "feature" feature (sigh) along side the official navigation structure.

The essence of it is to provide a navigational structure designed and maintained by ERA admin, in contrast to any user-created collections that might arise. But we know that ERA admin might also have collections that don't belong in this structure (but which might still be public, so the "publish" label might be confusing). Maybe "bless"/"unbless"?

Peter

On 3 March 2015 at 15:28, pgwillia notifications@github.com wrote:

How about curate and weed instead of publish/un-publish, feature/un-feature or official/unofficial?

— Reply to this email directly or view it on GitHub <

https://github.com/ualbertalib/HydraNorth/issues/76#issuecomment-77050808>

.

— Reply to this email directly or view it on GitHub < https://github.com/ualbertalib/HydraNorth/issues/76#issuecomment-77054510> .

Geoff Harder Associate University Librarian Information Resources and Digital Initiatives

University of Alberta Libraries

2-10H Cameron Library, University of AlbertaEdmonton, AB, Canada T6G 2J8 780.492.7914 geoffrey.harder@ualberta.ca geoffrey.harder@ualberta.ca library.ualberta.ca http://library.ualberta.ca

— Reply to this email directly or view it on GitHub https://github.com/ualbertalib/HydraNorth/issues/76#issuecomment-77064254 .

Sharon Farnel Metadata Coordinator University of Alberta Libraries sharon.farnel@ualberta.ca 780-492-3685

pgwillia commented 9 years ago

https://github.com/projecthydra-labs/hydra-collections/issues/58

pgwillia commented 9 years ago

This issue changed significantly with the decision to remove admin functionality from the front page. My understanding of how this will be handled is that links to desired "official" collections will be hard coded into the front page of the application. The existing collections display page functionality plus the ability to nest collections is sufficient for collection browsing. The batch ingest/migration of collections will provide the content to link to.

I think this issue can be closed as a result of these decisions.

pbinkley commented 9 years ago

I agree - we'll just need to coordinate with Natasha on who will implement this functionality as part of the structure of second-level browse pages.

pbinkley commented 9 years ago

We need to check with Natasha - we think that all that's needed is styling work from Natasha. @nnunn , please check with Chris about this.

pbinkley commented 9 years ago

Sonya will flesh out the presentation requirements for this functionality.

nnunn commented 9 years ago

Community page is now up and working.