Bug 5065 - ability to choose framework on import
Summary: ability to choose framework on import
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: All All
: PATCH-Sent (DO NOT USE) enhancement (vote)
Assignee: Frédéric Demians
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-27 19:56 UTC by Nicole C. Engard
Modified: 2012-10-25 23:04 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Proposed patch (6.80 KB, patch)
2011-03-18 18:00 UTC, Frédéric Demians
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2010-07-27 19:56:19 UTC
When using the import tool in Koha for importing MARC your records are automatically assigned the default framework, it would be nice if there was a choice on the import of what template to use for the records you're importing.
Comment 1 Nicole C. Engard 2010-07-27 19:59:01 UTC
I meant a choice of what 'framework' to use.
Comment 2 Frédéric Demians 2011-03-18 16:25:07 UTC
Nicole, are you working on this? I have this enhancement demand from a
customer and may develop it soon. 

There is also a related demand: On pro interface search result page,
there is a link 'Edit record'. This link would be expandable (like top
'More' link) to allow to choose another framework to edit the biblio
record in. The goal is to avoid to open biblio in Default framework
which is huge and so slow to be loaded.
Comment 3 Owen Leonard 2011-03-18 17:07:58 UTC
> There is also a related demand: On pro interface search result page,
> there is a link 'Edit record'. This link would be expandable (like top
> 'More' link) to allow to choose another framework to edit the biblio
> record in.

If you changing it there, you should probably also change the edit menu on the detail page. Maybe something like this:

Edit Record
Edit Record As...
Edit Items
[..etc...]

...and have the "Edit Record As..." option open a sub-menu. I usually avoid sub-menus because I like to keep things simple, but this is probably a good use of them given it's an advanced option.

How did you plan to create the menu on the search results page? YUI is currently the standard for creating menus in Koha since the jQueryUI component isn't ready yet.
Comment 4 Frédéric Demians 2011-03-18 17:50:24 UTC
> If you changing it there, you should probably also change the edit
> menu on the detail page. Maybe something like this:

> Edit Record
> Edit Record As...
> Edit Items
> [..etc...]

> ...and have the "Edit Record As..." option open a sub-menu. I usually
> avoid sub-menus because I like to keep things simple, but this is
> probably a good use of them given it's an advanced option.

You're correct. Thanks for pointing into the right direction. 

> How did you plan to create the menu on the search results page? YUI is
> currently the standard for creating menus in Koha since the jQueryUI
> component isn't ready yet.

I have in mind a lightweight menu, like the one used for More option on
Koha top menu bar. And I'm even reluctant to do it now because it
would imply using HTML::Template. I'd prefer to wait Template Toolkit.

This discussion should be moved to a new enhancement bug.
Comment 5 Frédéric Demians 2011-03-18 18:00:49 UTC
Created attachment 3351 [details] [review]
Proposed patch
Comment 6 Chris Cormack 2011-03-21 07:38:32 UTC
Patch pushed, please test