I am testing out Fedora 3.1 ingests in preparation for our migration. In order for us to migrate to 3.1, our workflow requires that the commandline tools all be functional.
What I have found so far is that I can get a batch to build with the commandline. I can also get some of those batches to ingest either via the command line or via the GUI. However, most other batches can ingest via the GUI, but via the command line give me only the error message "Error : 1", without logging any messages elsewhere in the system. (As a probably unrelated aside, I noticed the same problem when doing batch modifies when we moved from Fedora 2.2.2 to Fedora 2.2.4, but we do batch modifies rarely enough that I was willing to live with the difficulty of having to use the GUI.) The error messages so uninformative I'm not even sure what other information to provide in order to debug. I could attach an example of a batch which succeeds and another batch which fails? But under what circumstances would the CLI fail and the GUI succeed? As far as I can tell their settings are identical: repository, port, foxml version, username, password. (One of the difficulties is that this "Error : 1" seems to be turning up an awful lot of the time for a whole slew of problems: duplicate pid, wrong foxml version, incorrect password. So it's really hard to debug what it means.) -- Deborah Kaplan Digital Resources Archivist Digital Collections and Archives Tufts University ------------------------------------------------------------------------------ _______________________________________________ Fedora-commons-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
