Request: Accept semicolon delimited string in Collection field for Wonderfetch in BIblio
Bug #712694 reported by
Jude Coelho
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Scribe2 |
New
|
Undecided
|
danh |
Bug Description
With the new registered collection system (http://
This change is needed for a new version of the Wonderfetch Template to be released.
Changed in scribe2: | |
assignee: | nobody → danh (danh-archive) |
To post a comment you must log in.
Jude Coelho wrote: yaz.us. archive. org/biblio. php?f=collectio ns_edit) it would be
> Public bug reported:
>
> With the new registered collection system
> (http://
> 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