Concerto dataset's acq data should include more elements
Bug #1545185 reported by
Galen Charlton
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Rather than leave bug 1486294 in a partially completed state, I'm opening a new bug for additional data elements that would be good to have in the Concerto dataset:
* received PO's
* invoices
Revision history for this message
| Chris Sharp (chrissharp123) wrote | #1 |
| tags: | added: acq sampledata |
To post a comment you must log in.
While were at it... We found something yesterday that we will be reporting a bug on soon that was elicited by having a selection list long enough for paging to occur. So my wish for the test data is that it would include longer lists of things in an attempt to reflect real-life usage.
I'd love to see a way to simulate and/or actually test EDI, but since much of that is vendor-specific and requires real processing on the vendor end, that may be impractical. At the very least though, I'd like to see concerto Acq MARC record files that could be uploaded to create a new PO/selection list within a concerto-based test server.
(If these musing deserve their own bug(s), I'd be happy to open them)