Wonderfetch fields don't work in Mode3 with Post-BiblioFetch

[Jude Coelho]

When trying to make changes to items using post-bibliofetch in Mode 3 (roll your own), wonderfetch values (w_language, etc) are not accepted via URL.

Example: http://yaz.us.archive.org/biblio.php?w_wonderfetch=1&f=un_biblio&b_l=Clemson%20University%20Libraries&b_c1=clemson&b_c2=americana&b_n=nj&b_p=Lyrasis%20Members%20and%20Sloan%20Foundation&b_v=1965&pcs=Copyright%20of%20Clemson%20University.%20Use%20of%20materials%20from%20this%20collection%20beyond%20the%20exceptions%20provided%20for%20in%20the%20Fair%20Use%20and%20Educational%20Use%20clauses%20of%20the%20U.S.%20Copyright%20Law%20may%20violate%20federal%20law.%20Permission%20to%20publish%20or%20reproduce%20is%20required.&lic=&rights=&dd=&b_rtl=&b_plt=&w_title=Taps&w_language=eng&add=1&w_subject=Clemson%20University--Students--Yearbooks;%20Clemson%20Agricultural%20College%20of%20South%20Carolina--Students--Yearbooks.&w_date=1965&w_publisher=Clemson%20University&w_description=%20%22Annual%20publication%20of%20Clemson%20University%22;%20June%201899%20and%201900%20issues%20of%20Clemson%20College%20Chronicle%20began%20the%20series%20of%20Clemson%20University%20yearbooks%20followed%20by%20the%20Clemsonian%20in%201901;%20%20the%20May%20issue%20of%20Clemson%20College%20Chronicle%20in%201902;%20the%20Oconeean%20in%201903-1904;%20the%20May%20issue%20of%20the%20Chronicle%20in%201905;%20the%20Clemson%20College%20annual%20in%201906-1907;%20beginning%20in%201908%20to%20the%20present,%20as%20Taps;%20no%20issues%20published%20from%201944-1946,%20information%20about%20graduates,%20etc.%20were%20published%20in%201947;%20subtitle%20varies.&w_creator=Clemson%20University&b_c3=X0000&b_cl=&b_sf=&b_id=taps1965clem&c[0]=call_number&v[0]=LD1087%20.T1

If we could fix this, we would be closer to a new version of Wonderfetch that could eliminate bad tasks being submitted by people using Mode4 (need to look at any possible issues caused by using post-biblio-fetch on derived items).

-Jude

[Hank Bromley (hank-archive)]

The following are the fields that are not yet properly dealt with by post-biblio fetch (as best I recall, anyway; I know these are the affected fields, but my notes were vague on exactly what goes wrong with each of them):

noindex gets unconditionally set to true

uploader gets set to the submitter of the post-biblio, in place of the original loader

identifier-access gets wiped

description gets set to the description fields (datafields 5xx) in the new record, which is correct *if* description had contained only what was in the old 5xx fields, but sometimes additional, non-MARC-derived, info is in the description field that should be kept, along with the new 5xx fields

[Jude Coelho (judec)]

We should also confirm that the Wonderfetch fields carry though in Mode1
and Mode2, and the custom pairs as well.

[Jude Coelho (judec)]

I'm seeing issues where, using post-bibliofetch, previously filled fields in meta.xml are not carrying over to the new form.

[Jude Coelho (judec)]

When I get to SF and take over as process manager, I'd like to get a new version of Wonderfetch out to resolve and simplify a lot of issues. Assigning this to myself to be dealt with when I get out there in about a month.

[Jude Coelho (judec)]

Moving this to Scribe2.