[Koha-bugs] [Bug 33932] Why multiple statuses on item record

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33932

--- Comment #7 from David Cook <dcook at prosentient.com.au> ---
(In reply to Christopher Brannon from comment #5)
> (In reply to Jonathan Druart from comment #4)
> > Everything is always possible, but that would be really hard to change :)
> 
> Everything is hard to change from my perspective, especially mechanisms that
> have been in place for years, but there is a community of programmers out
> there that put together a brilliant ILS from nothing.  Complexity should not
> be the deciding factor.  I'm sure that answer could be given to most of the
> things the community programmers have contributed to Koha over the last 23
> years.

Considering that Jonathan Druart is the number 1 top contributor to Koha by a
landslide, you can trust his authority on the feasibility of changes. 

Koha also doesn't come from nothing. While many of us community programmers
have volunteered our own time at times out of the goodness of our hearts, a lot
of the work we do is paid for by our employers or our clients. Someone has
decided that the change was valuable enough to pay for our time. 

A contribution isn't just writing code either. It's also seeing it through an
additional 3 step process of testing, quality assurance, and merging/pushing.
At that point, it's not just 1 person's time, but 4 people's time involved in
making just 1 contribution go into Koha. 

Small contributions are easy to get through the process, but complex ones are
more challenging. Jonathan has contributed quite a few complex changes to Koha,
and helped other people with theirs.

Something like item "status" is complicated even further than many complex
changes, because that's something that gets shared beyond Koha via APIs to
discovery systems like VuFind, Aspen, EBSCO's EDS, Ovid's ODS, etc. 

--

That said, there is more than one way to look at a problem as well. Perhaps
what you have in mind is more of a change to how the data is "viewed" rather
than how the data is "modelled".

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.