28.06.2013 Views

Papers in PDF format

Papers in PDF format

Papers in PDF format

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Let’s look at the contrast<strong>in</strong>g qualities and attributes between the traditional pyramid and the evolv<strong>in</strong>g web as<br />

models of organisational structure.<br />

Pyramid Web<br />

Rigid Hierarchies Flexible Teams<br />

Isolation of Power Shared Responsibility<br />

Fragmentation Integration<br />

Control Open Access<br />

Rigid Hierarchies vs. Flexible Teams<br />

Top-down organisations are usually not very agile when it comes to respond<strong>in</strong>g to and more importantly,<br />

manag<strong>in</strong>g change. And change is now a constant <strong>in</strong> the <strong>in</strong><strong>format</strong>ion marketplace. Flexible teams which<br />

<strong>in</strong>teract to develop a library’s Web will be better situated to perceive change <strong>in</strong> client groups and the <strong>in</strong>dustry<br />

and can thereby <strong>in</strong>corporate it as necessary. Fluid boundaries support <strong>in</strong>terdiscipl<strong>in</strong>ary projects, the structure<br />

flattens and all participate <strong>in</strong> the creation of an enriched environment of discovery and disclosure.<br />

Isolation of Power vs. Shared Responsibility<br />

The concentration of power <strong>in</strong> a pyramid is at the narrow top. Quite often <strong>in</strong> these structures decisions have to<br />

make their way from the bottom up through each hierarchical layer until they sometimes f<strong>in</strong>d their way to the<br />

top by which time of course the plot may well be lost. In us<strong>in</strong>g the work<strong>in</strong>g group or team model which<br />

succeeds <strong>in</strong> the process of Web development, responsibility gets shared across the structure. Senior<br />

management must lead the organisation with a client based focus, ensure that they hire capable staff, tra<strong>in</strong> and<br />

retra<strong>in</strong> when required, and then let the staff get on with it.<br />

Fragmentation vs. Integration<br />

Traditional departmental structures have segregated processes <strong>in</strong> the name of procedure, and often these<br />

procedures are based on ext<strong>in</strong>ct systems such as a card catalogue <strong>in</strong> a library. More importantly, departmental<br />

structure has <strong>in</strong> many cases fostered destructive competition, <strong>in</strong>equities and ultimately, the clientele has been<br />

lost from sight. As systems or IT units have been <strong>in</strong>troduced <strong>in</strong> libraries, they have typically been set up as yet<br />

another department. Technology is no longer a trend or phenomenon; it needs to be seen as just one of a<br />

number of components which are seamlessly <strong>in</strong>tegrated <strong>in</strong>to the operations of <strong>in</strong><strong>format</strong>ion based services and<br />

digital libraries. What’s needed is “<strong>in</strong><strong>format</strong>ion systems research, <strong>in</strong>stead of computer technology research.<br />

Digital libraries need to be tested with large collections and users s<strong>in</strong>ce the value of the technology cannot be<br />

evaluated <strong>in</strong> isolation." [Schatz 1995 [HREF4]]<br />

Control vs. Open Access<br />

Control from the pyramid “tower” may have worked or at least appeared to work when the ma<strong>in</strong> bus<strong>in</strong>ess of<br />

<strong>in</strong><strong>format</strong>ion based services such as libraries was handl<strong>in</strong>g physical objects. In those days <strong>in</strong><strong>format</strong>ion was a<br />

f<strong>in</strong>ite set of items. In the digital library we have moved to manag<strong>in</strong>g bits not atoms [Negroponte 1995].<br />

Management is now responsible for mak<strong>in</strong>g accessible to its clientele an expand<strong>in</strong>g, widely distributed and<br />

very complex network of <strong>in</strong><strong>format</strong>ion objects <strong>in</strong>clud<strong>in</strong>g databases, software, <strong>in</strong>terfaces, metadata and people.<br />

Not only do the clients need an open access structure, but also the staff will have to have such an environment<br />

<strong>in</strong> order to move the organisation forward.<br />

Libraries have been utilis<strong>in</strong>g technology for decades now, but the developments <strong>in</strong> the distribution of<br />

<strong>in</strong><strong>format</strong>ion via the Internet and more specifically the World Wide Web have profound implications <strong>in</strong>clud<strong>in</strong>g<br />

major shifts <strong>in</strong> the responsibilities of libraries. Technology will have to be truly <strong>in</strong>tegrated and managed by the

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!