Its time to decide how we want Biblio Collections to work.

I've set a Whiteboard up here: http://123.writeboard.com/eb64b5982e733fde9

Please drop by and edit it to tell me what you want Biblio Collections to be.

If you don't want to Whiteboard it, here is a copy of my initial questions..



Biblio Collections

Biblio is a drupal module which stores scholarly publication information. Biblio provides css (cascading stylesheets) for popular citation formats (e.g., APA, IEEE, etc.).

Biblio requires each citation be assigned a content type (e.g., journal article, book, etc.)

Biblio Collections would provide the ability to conveniently group publications. This document serves as the specifications of HOW biblio collections will be implemented.
-—-
Biblio Admin
1. There will be a collapsible entry on the Biblio Admin Settings page.
2. The following entries will be on the collapsible entry:

You can alter collections related settings here.
Allow users to see collections tab
This will allow the collections tab to be available within biblio settings

Allow collections to have different formats
This option will permit each collection to present in a different format (e.g., MLA, APA, etc.).

Collections access
This is something to do with access i think i need for organic groups integration.

3. Do we want the admin to limit the formats available for the user/site to use on collections?

Biblio Admin Questions:
1. Do we allow admins to create collections for the site?
2. If we allow admins to create sitewide collections, do we also allow users to have their own collections?
3. If we allow admins AND users to create collections, how do we differentiate between a user collection and a sitewide collection. For viewing? For editing?

Biblio User Collections
1. Is there a limit to the number of collections a user can create?
2. Do we want the admin to limit the number of collections a user can create?
3. Where do we want the User collections to show up? Is this a tab on the user profile? Is this a new biblio page? Is this a link next to LIST/FILTER → LIST / FILTER /COLLECTION when you go to the standard …/biblio page?
4. Where do you want the User to create the collections? Is this a new biblio page? If so, where do I put the link? Is this on the user profile page?

Biblio Collections User Interface
1. What do you want the interface to look like to add nodes (biblio entries) to a collections? Is this a comprehensive site list with a checkbox beside each entry? Is this a drag and drop (left pane to right pane)? Is this a cntl+shift highlight and click button add/remove to collection?
2. Once added to the collection, what do we provide for sorting? Any biblio field or some subset or just let them use handlers and move things around.
3. Do we provide a button to ‘add all my own entries’ to the collection or ‘add all entries of a certain publication type or author ??’

Biblio Collections tables
From Capn R when I first brought up the subject:
quote::
The way I was looking at it is very much like a hierarchical taxonomy
vocabularies where the vocabulary is a collection and each collection
can contain pointers to nodes or other (sub) collections. You will
find a biblio_collection table which contains cid,vid,pid,nid these
are “Collection id”, “(node)Version id”, “Parent collection id”, and
“node id” respectively. Another table, biblio_collection_type, has
the “cid”, “name”, “description” for each collection. In theory
(since I haven’t actually tried it yet) you should be able to
construct a hierarchical collection with these two tables.
unquote

The issue I currently see is that cid is the key for biblio collections table. But on the contributor table, cid is also the key there. What should the key be on the collections table? If we leave it as cid on both tables, tell me what you prefer to see in the coding when I rename the collections id so I can keep it straight on the sql.

Style format .
I will need to add style to the top level of the collections table.
If there is no style assigned or it gets corrupted, we will default it to the system sitewide format.

List
1.Won’t we need to have one of the collections defined as the ‘default’ to use for the generic /biblio page?

Views
1. How do you se this working with Views and Views filter/sorting etc?

Comments

Thomas_Zahreddin’s picture

Category: task » feature
Issue tags: +collection

i like the idea and i'm willing to test / contribute :-)

i solved it in the moment with a taxonomy to tag the items for each collection.

Aren Cambre’s picture

Thomas is the right track. Once #682044: Support fields (CCK) in D7 Bibliography Module is fulfilled, this collections concept will be easily doable with taxonomy or one or more CCK fields and Views with filters.

All the permissions/limitations can probably be implemented with standard modules.

bekasu’s picture

I appreciate your observations on Biblio Collections.

#1 I'll let you know when I have things a bit further along

#2 Good luck with your approach

rmh3093’s picture

What is the status of this? I really need a way to group my biblio entries apap.

bekasu’s picture

I have got the code completed to allow 1 sitewide list.
I have the first part of the code for the 'catalog' - listings of collections.

I've completed the admin interface for setting the default style for each collection, name of the collection, etc.

Left to do:
1. Separate pages for creating or deleting collections.
2. Coordinating handoff from Biblio for tables (biblio colections tables will no longer be created by biblio once this is complete)
3. Styles - Biblio is changing the way they implement styles (different file locations, etc.) - collections doesn't know about this yet.
4. Help documentation - Biblio will be implementing advanced help and Biblio Collections will be using advanced Help.
5. Allow individual users to have their own collections.

Mr. Ron and I are trying to stay coordinated on this one.

Personal items have been in the forefront of late; however, I'm looking toward April for testing.

I'd be interested in knowing how YOU would be using collections. I've had very little guidance and would like to be sure I'm not overlooking something.

bekasu

rmh3093’s picture

So I run a website for our Lab and on this site we would like to have a few collections of biblios. First we want a public collection to show of all the publications that are associated with our lab members... so a "our publications" collection. We would also like a private collection to put random interesting journal articles in that we not necessarily written by a lab member. Additionally, I need to host archives of 2 journals in their own collections that may or may not need some sort of ACL or regulated access.

Hope that is a good example for you. Looking forward to testing any code when its ready.

bekasu’s picture

rmh3093 - how do you envision the process for adding entries to the publications? Is this only by the admin, or by a member? Seems like you might like one of each - a more restrictive, admin only collection as well as a couple of collections that can be 'updated' by members (or a subset of members?).

Want to be sure I get permissions access to handle the 'needs'. I know what I need, but want to be sure I add enough flexibility if you need something a little different.

I'll keep you in mind for testing, thank you.

rmh3093’s picture

Add to collection by role... maybe collections could be based on taxonomy which already support many types of permissions/acl.

cindyr’s picture

Any update on where this stands? My needs are to have two fields, both node-reference bibliographies, in the same content type. My users create a project and use the node reference field to provide "supporting documentation" bibliographies. Then I need the users, at a different workflow state (after their project has been published), to be able to add a publication of type "published in:". The workflow fields module works great for cck fields, but it requires that I have two separate biblio cck fields to view.

Liam Morland’s picture

Status: Active » Closed (outdated)

This version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.