Request: Accept semicolon delimited string in Collection field for Wonderfetch in BIblio

[Jude Coelho]

With the new registered collection system (http://yaz.us.archive.org/biblio.php?f=collections_edit) it would be good if we could eliminate the dual collection submission interface from wonderfetch, which currently accepts one collection string in "collection" (b_c1), and multiple strings separated by semicolon in "subcollection" (b_c2). This is confusing for partners and loaders, and it would be better if we could just accept semicolon delimited strings in b_c1 and eliminate using b_c2 for wonderfetch at all (though we should simply deprecate it, not remove it, as outside partners may use this still).

This change is needed for a new version of the Wonderfetch Template to be released.

[danh (danh-archive)]

Jude Coelho wrote:
> Public bug reported:
>
> With the new registered collection system
> (http://yaz.us.archive.org/biblio.php?f=collections_edit) it would be
> good if we could eliminate the dual collection submission interface from
> wonderfetch, which currently accepts one collection string in
> "collection" (b_c1), and multiple strings separated by semicolon in
> "subcollection" (b_c2). This is confusing for partners and loaders, and
> it would be better if we could just accept semicolon delimited strings
> in b_c1 and eliminate using b_c2 for wonderfetch at all (though we
> should simply deprecate it, not remove it, as outside partners may use
> this still).
>
> This change is needed for a new version of the Wonderfetch Template to
> be released.
>
> ** Affects: scribe2
> Importance: Undecided
> Assignee: danh (danh-archive)
> Status: New
>
> ** Changed in: scribe2
> Assignee: (unassigned) => danh (danh-archive)
>

Is b_c1 mandatory?

That is, if you just leave it out, can you use b_c2 to hold
all the collections?

(My guess is that it really is mandatory, but have to be sure
before starting any mods.)

dan