Foreword |
|
ix | |
Preface |
|
xi | |
Acknowledgments |
|
xvii | |
Introduction |
|
xxxix | |
|
|
1 | (62) |
|
Defining Data, Information, and Content |
|
|
3 | (10) |
|
|
4 | (1) |
|
|
5 | (2) |
|
Content Is Information Put to Use |
|
|
7 | (4) |
|
Content Is Information Plus Data |
|
|
11 | (1) |
|
From Data to Content and Back |
|
|
11 | (1) |
|
|
12 | (1) |
|
|
13 | (8) |
|
Storage Formats: Storing Information |
|
|
13 | (1) |
|
Rendering Format: Presenting Information |
|
|
14 | (1) |
|
|
15 | (2) |
|
|
17 | (2) |
|
|
17 | (1) |
|
|
18 | (1) |
|
|
18 | (1) |
|
|
19 | (2) |
|
|
21 | (10) |
|
|
21 | (3) |
|
Structure Can Be Difficult to Create |
|
|
24 | (2) |
|
How to Categorize Structure |
|
|
26 | (3) |
|
|
27 | (1) |
|
|
27 | (1) |
|
|
28 | (1) |
|
|
29 | (2) |
|
Functionality Is Content, Too! |
|
|
31 | (10) |
|
|
31 | (1) |
|
Monolithic versus Mix-and-Match Functionality |
|
|
32 | (1) |
|
Functionality Interspersed with Information |
|
|
33 | (2) |
|
Managing Functionality Like Information |
|
|
35 | (5) |
|
Publishing functionality on the Web |
|
|
36 | (2) |
|
Where information and functionality diverge |
|
|
38 | (2) |
|
|
40 | (1) |
|
But What Is Content Really? |
|
|
41 | (22) |
|
Content, Context, and Meaning |
|
|
41 | (2) |
|
|
43 | (2) |
|
Content Organization Starts with Purpose |
|
|
45 | (2) |
|
Content Is Named Information |
|
|
47 | (2) |
|
|
49 | (10) |
|
|
49 | (2) |
|
Data is nondiscursive and out of context |
|
|
51 | (1) |
|
Information is processed and continuous |
|
|
52 | (2) |
|
Information is discursive and full of context |
|
|
54 | (3) |
|
Knowledge and wisdom can be information |
|
|
57 | (2) |
|
Why Does Text Get All of the Attention? |
|
|
59 | (3) |
|
Text is codified language |
|
|
60 | (1) |
|
|
61 | (1) |
|
|
62 | (1) |
|
Part II: What Is Content Management? |
|
|
63 | (136) |
|
Understanding Content Management |
|
|
65 | (20) |
|
Defining Content Management |
|
|
65 | (2) |
|
CM Is Distributing Business Value |
|
|
67 | (2) |
|
CM Is a Balance of Organizational Forces |
|
|
69 | (1) |
|
CM Is the Combination of Content-Related Disciplines |
|
|
70 | (2) |
|
CM Is Collection, Management, and Publishing |
|
|
72 | (2) |
|
CM Is a Computer Infrastructure |
|
|
74 | (8) |
|
|
75 | (1) |
|
|
75 | (2) |
|
|
77 | (2) |
|
|
79 | (2) |
|
|
81 | (1) |
|
The Content Management Industry |
|
|
82 | (1) |
|
|
83 | (2) |
|
Introducing the Major Parts of a CMS |
|
|
85 | (28) |
|
|
86 | (1) |
|
|
87 | (13) |
|
|
88 | (1) |
|
|
89 | (3) |
|
|
92 | (1) |
|
|
93 | (6) |
|
|
99 | (1) |
|
|
100 | (6) |
|
|
100 | (3) |
|
The administration system |
|
|
103 | (2) |
|
|
105 | (1) |
|
|
105 | (1) |
|
|
106 | (5) |
|
|
106 | (2) |
|
|
108 | (1) |
|
|
108 | (1) |
|
|
109 | (2) |
|
|
111 | (1) |
|
|
111 | (2) |
|
Knowing When You Need a CMS |
|
|
113 | (18) |
|
Gauging the Amount of Content |
|
|
114 | (1) |
|
Managing the Size of the Contribution Base |
|
|
115 | (2) |
|
Anticipating the Amount of Change |
|
|
117 | (2) |
|
Knowing the Number of Publications |
|
|
119 | (2) |
|
|
121 | (8) |
|
|
123 | (1) |
|
|
124 | (1) |
|
|
125 | (1) |
|
|
126 | (2) |
|
|
128 | (1) |
|
|
129 | (2) |
|
Component Management versus Composition Management |
|
|
131 | (16) |
|
CM Systems Can Be Modular or Linear |
|
|
131 | (2) |
|
|
133 | (2) |
|
|
135 | (6) |
|
Collection in a composition system |
|
|
136 | (1) |
|
Management in a composition system |
|
|
137 | (1) |
|
Publication in a composition system |
|
|
138 | (3) |
|
|
141 | (4) |
|
Collection in a schema-driven system |
|
|
143 | (1) |
|
Management in a schema-driven system |
|
|
144 | (1) |
|
Publishing in a schema-driven system |
|
|
144 | (1) |
|
Which System Is Right for You? |
|
|
145 | (1) |
|
|
146 | (1) |
|
The Roots of Content Management |
|
|
147 | (26) |
|
The Knowledge Base of the Publishing Industry |
|
|
148 | (3) |
|
|
148 | (1) |
|
|
149 | (1) |
|
|
149 | (2) |
|
The Principles of Document Management |
|
|
151 | (4) |
|
|
152 | (1) |
|
|
153 | (1) |
|
|
153 | (1) |
|
Document management systems versus content management systems |
|
|
154 | (1) |
|
The Limits of Information Technology Groups |
|
|
155 | (2) |
|
IT departments have avoided the Web |
|
|
156 | (1) |
|
Content begins where IT groups leave off |
|
|
156 | (1) |
|
The Legacy of the Multimedia Industry |
|
|
157 | (3) |
|
|
159 | (1) |
|
End-to-end content management |
|
|
159 | (1) |
|
The Challenges of Technical Communication |
|
|
160 | (3) |
|
|
160 | (2) |
|
Simultaneous publications |
|
|
162 | (1) |
|
|
163 | (1) |
|
The Traditions of Library and Information Science |
|
|
164 | (4) |
|
|
164 | (1) |
|
|
165 | (1) |
|
|
165 | (1) |
|
|
166 | (2) |
|
The Technology of Software Development |
|
|
168 | (3) |
|
|
168 | (1) |
|
|
168 | (1) |
|
|
168 | (1) |
|
The functionality in electronic publications |
|
|
169 | (2) |
|
The Premises of Marketing |
|
|
171 | (1) |
|
|
172 | (1) |
|
The Branches of Content Management |
|
|
173 | (26) |
|
|
174 | (3) |
|
|
174 | (2) |
|
Content management underlies personalization |
|
|
176 | (1) |
|
|
177 | (2) |
|
|
179 | (3) |
|
|
182 | (3) |
|
Catalogs and content management |
|
|
183 | (1) |
|
E-commerce functionality and content management |
|
|
184 | (1) |
|
|
185 | (2) |
|
What is knowledge management? |
|
|
185 | (1) |
|
Knowledge is content to manage |
|
|
186 | (1) |
|
|
187 | (6) |
|
|
188 | (1) |
|
How are online communities constructed? |
|
|
188 | (5) |
|
Other Kinds of Management |
|
|
193 | (5) |
|
Digital asset management (DAM) |
|
|
195 | (1) |
|
Learning object management (LOM) |
|
|
195 | (1) |
|
|
195 | (1) |
|
Digital records management |
|
|
196 | (1) |
|
Digital rights management (DRM) |
|
|
197 | (1) |
|
|
198 | (1) |
|
Part III: Doing Content Management Projects |
|
|
199 | (252) |
|
|
201 | (18) |
|
Why Create a Minimal CMS? |
|
|
201 | (2) |
|
|
203 | (2) |
|
|
203 | (1) |
|
|
204 | (1) |
|
|
204 | (1) |
|
|
205 | (1) |
|
Getting Ready for the Project |
|
|
205 | (4) |
|
Exploring the organization |
|
|
206 | (1) |
|
Finding the right project |
|
|
207 | (1) |
|
Finding the right sponsors |
|
|
207 | (1) |
|
|
208 | (1) |
|
Key planning deliverables |
|
|
209 | (1) |
|
|
209 | (2) |
|
Getting minimum requirements |
|
|
209 | (1) |
|
Logical design essentials |
|
|
210 | (1) |
|
|
210 | (1) |
|
|
211 | (6) |
|
|
211 | (3) |
|
Slimming down product selection |
|
|
214 | (1) |
|
|
214 | (1) |
|
Key implementation processes |
|
|
215 | (1) |
|
Key implementation deliverables |
|
|
216 | (1) |
|
|
217 | (1) |
|
|
217 | (1) |
|
Key deployment deliverables |
|
|
218 | (1) |
|
|
218 | (1) |
|
|
219 | (24) |
|
|
219 | (2) |
|
|
221 | (3) |
|
|
221 | (2) |
|
|
223 | (1) |
|
|
223 | (1) |
|
|
224 | (1) |
|
|
225 | (3) |
|
|
226 | (1) |
|
|
227 | (1) |
|
|
228 | (3) |
|
|
229 | (1) |
|
|
230 | (1) |
|
Trainer and documentation specialist |
|
|
231 | (1) |
|
|
231 | (3) |
|
|
231 | (1) |
|
Template and CMS developer |
|
|
232 | (1) |
|
Custom application developer |
|
|
232 | (1) |
|
|
233 | (1) |
|
Test analyst and test engineer |
|
|
233 | (1) |
|
|
234 | (3) |
|
|
234 | (1) |
|
|
235 | (1) |
|
|
236 | (1) |
|
User interface specialist |
|
|
237 | (1) |
|
|
237 | (2) |
|
|
237 | (1) |
|
|
238 | (1) |
|
|
239 | (1) |
|
|
239 | (1) |
|
|
239 | (2) |
|
|
240 | (1) |
|
|
240 | (1) |
|
Writers and other content creators |
|
|
240 | (1) |
|
|
241 | (1) |
|
|
241 | (2) |
|
Working within the Organization |
|
|
243 | (28) |
|
Content Management and the Organization |
|
|
243 | (4) |
|
Content Management versus Other Systems |
|
|
247 | (1) |
|
Tracking Information Flow in the Organization |
|
|
247 | (4) |
|
Understanding your information |
|
|
249 | (1) |
|
Understanding your functionality |
|
|
249 | (2) |
|
Understanding Organizational Roles |
|
|
251 | (2) |
|
Business units generate value |
|
|
251 | (1) |
|
Editorial teams unify content |
|
|
251 | (1) |
|
Marketing teams direct and unify publications |
|
|
252 | (1) |
|
IT groups build and maintain infrastructure |
|
|
253 | (1) |
|
|
253 | (3) |
|
|
253 | (1) |
|
|
254 | (1) |
|
|
254 | (1) |
|
|
255 | (1) |
|
|
255 | (1) |
|
Exploring Organizational Models |
|
|
256 | (7) |
|
|
257 | (1) |
|
|
258 | (3) |
|
|
261 | (2) |
|
Using Functional Collection and Publishing |
|
|
263 | (4) |
|
Organizing collection systems and publications by type |
|
|
263 | (1) |
|
Creating functional teams |
|
|
264 | (3) |
|
Identifying Your CMS Hurdles |
|
|
267 | (3) |
|
|
270 | (1) |
|
|
271 | (18) |
|
|
271 | (1) |
|
Understanding the CMS Project Process |
|
|
272 | (2) |
|
Techniques for Getting the Job Done |
|
|
274 | (7) |
|
Start with the project team |
|
|
275 | (2) |
|
Look for pain in the organization |
|
|
277 | (1) |
|
Assess the current mandate |
|
|
278 | (1) |
|
Assess the organization's assumptions |
|
|
278 | (3) |
|
Taking Stock of the Deliverables |
|
|
281 | (7) |
|
|
281 | (2) |
|
Document inventory and analysis |
|
|
283 | (1) |
|
The state-of-the-content system report |
|
|
284 | (1) |
|
|
285 | (1) |
|
A preliminary project plan |
|
|
286 | (1) |
|
|
287 | (1) |
|
Taking Stock of Your Staffing Needs |
|
|
288 | (1) |
|
|
288 | (1) |
|
Securing a Project Mandate |
|
|
289 | (14) |
|
|
289 | (1) |
|
|
290 | (1) |
|
Techniques for Getting the Job Done |
|
|
291 | (3) |
|
|
291 | (2) |
|
Learn about your sponsors |
|
|
293 | (1) |
|
Taking Stock of the Deliverables |
|
|
294 | (8) |
|
|
294 | (1) |
|
|
295 | (1) |
|
|
295 | (1) |
|
|
296 | (3) |
|
|
299 | (3) |
|
Taking Stock of Your Staffing Needs |
|
|
302 | (1) |
|
|
302 | (1) |
|
Doing Requirements Gathering |
|
|
303 | (12) |
|
|
303 | (1) |
|
|
304 | (1) |
|
Techniques for Getting the Job Done |
|
|
304 | (7) |
|
|
305 | (1) |
|
|
306 | (4) |
|
Approaching the organization |
|
|
310 | (1) |
|
Taking Stock of the Deliverables |
|
|
311 | (2) |
|
The requirements plan of attack |
|
|
312 | (1) |
|
The requirements document |
|
|
312 | (1) |
|
Taking Stock of Your Staffing Needs |
|
|
313 | (1) |
|
|
313 | (2) |
|
|
315 | (26) |
|
|
315 | (1) |
|
|
316 | (2) |
|
Techniques for Getting the Job Done |
|
|
318 | (7) |
|
|
319 | (1) |
|
|
320 | (2) |
|
Iterating through your design |
|
|
322 | (1) |
|
Triangulating on constraints |
|
|
323 | (2) |
|
|
325 | (1) |
|
Taking Stock of the Deliverables |
|
|
325 | (13) |
|
The design plan of attack |
|
|
326 | (1) |
|
The collection design document |
|
|
327 | (1) |
|
The management design document |
|
|
328 | (2) |
|
The publication design documents |
|
|
330 | (2) |
|
|
332 | (1) |
|
|
333 | (2) |
|
|
335 | (1) |
|
|
336 | (1) |
|
|
337 | (1) |
|
Taking Stock of Your Staffing Needs |
|
|
338 | (1) |
|
|
339 | (2) |
|
Selecting Hardware and Software |
|
|
341 | (58) |
|
System Selection Jumpstart |
|
|
341 | (2) |
|
|
343 | (5) |
|
|
348 | (3) |
|
|
348 | (1) |
|
|
349 | (1) |
|
|
349 | (2) |
|
Techniques to Get the Job Done |
|
|
351 | (13) |
|
How to select decision makers |
|
|
351 | (2) |
|
|
353 | (11) |
|
Taking Stock of the Deliverables |
|
|
364 | (3) |
|
|
364 | (1) |
|
The selection criteria and RFP |
|
|
364 | (1) |
|
|
365 | (1) |
|
|
365 | (1) |
|
|
366 | (1) |
|
|
366 | (1) |
|
|
367 | (1) |
|
Taking Stock of Your Staffing Needs |
|
|
367 | (2) |
|
Sorting Through the CMS Selection Criteria |
|
|
369 | (28) |
|
|
370 | (1) |
|
|
371 | (6) |
|
|
377 | (5) |
|
|
382 | (8) |
|
|
390 | (7) |
|
|
397 | (2) |
|
|
399 | (30) |
|
Implementing the System Jumpstart |
|
|
399 | (2) |
|
Looking at the Process So Far |
|
|
401 | (1) |
|
Looking at the Project So Far |
|
|
401 | (1) |
|
Techniques for Getting the Job Done |
|
|
402 | (16) |
|
|
402 | (1) |
|
Do you have one project or many projects? |
|
|
403 | (2) |
|
Detailing the implementation process |
|
|
405 | (13) |
|
Taking Stock of the Deliverables |
|
|
418 | (9) |
|
Collection specifications |
|
|
420 | (1) |
|
Management specifications |
|
|
421 | (1) |
|
Publication specifications |
|
|
422 | (2) |
|
|
424 | (2) |
|
|
426 | (1) |
|
Taking Stock of Your Staffing Needs |
|
|
427 | (1) |
|
|
427 | (2) |
|
|
429 | (22) |
|
Rolling Out the System Jumpstart |
|
|
429 | (1) |
|
|
430 | (1) |
|
Techniques to Get the Job Done |
|
|
431 | (15) |
|
|
431 | (6) |
|
|
437 | (3) |
|
|
440 | (4) |
|
|
444 | (1) |
|
|
444 | (2) |
|
Taking Stock of the Deliverables |
|
|
446 | (4) |
|
The deployment specification |
|
|
446 | (1) |
|
|
447 | (1) |
|
|
447 | (1) |
|
|
448 | (1) |
|
|
449 | (1) |
|
|
450 | (1) |
|
|
451 | (340) |
|
|
453 | (6) |
|
Logical Design Essentials |
|
|
453 | (1) |
|
|
454 | (1) |
|
Logical Design: An Example |
|
|
455 | (3) |
|
Plan International---an example organization |
|
|
455 | (1) |
|
A very simple logical design |
|
|
455 | (3) |
|
Getting Beyond the Simple Logical design |
|
|
458 | (1) |
|
|
458 | (1) |
|
The Wheel of Content Management |
|
|
459 | (32) |
|
The Content Management Entities |
|
|
459 | (29) |
|
Introducing the CMS wheel |
|
|
461 | (2) |
|
Entities add a layer of abstraction |
|
|
463 | (1) |
|
|
464 | (4) |
|
|
468 | (3) |
|
|
471 | (3) |
|
|
474 | (4) |
|
|
478 | (2) |
|
|
480 | (3) |
|
|
483 | (1) |
|
|
484 | (4) |
|
|
488 | (1) |
|
|
489 | (2) |
|
|
491 | (26) |
|
|
491 | (7) |
|
|
491 | (1) |
|
|
492 | (2) |
|
What does metatorial mean? |
|
|
494 | (2) |
|
The narrow view of metadata |
|
|
496 | (1) |
|
The wide view of metadata |
|
|
496 | (1) |
|
Metadata and content management |
|
|
497 | (1) |
|
Understanding the Types of Metadata |
|
|
498 | (8) |
|
|
498 | (2) |
|
|
500 | (2) |
|
|
502 | (1) |
|
|
503 | (1) |
|
|
504 | (2) |
|
Categorizing Metadata Fields |
|
|
506 | (2) |
|
|
508 | (6) |
|
|
510 | (1) |
|
|
511 | (3) |
|
|
514 | (1) |
|
|
515 | (2) |
|
|
517 | (20) |
|
Cataloging Audiences Jumpstart |
|
|
517 | (1) |
|
Serving versus Exploiting an Audience |
|
|
518 | (2) |
|
|
520 | (3) |
|
Audiences and communicators |
|
|
520 | (1) |
|
|
521 | (1) |
|
|
522 | (1) |
|
How many audiences do you have? |
|
|
522 | (1) |
|
Audiences and Localization |
|
|
523 | (5) |
|
|
524 | (1) |
|
What are your localities? |
|
|
525 | (1) |
|
|
526 | (1) |
|
|
526 | (1) |
|
Localization and content management |
|
|
527 | (1) |
|
|
528 | (1) |
|
|
529 | (7) |
|
|
529 | (1) |
|
|
530 | (5) |
|
|
535 | (1) |
|
|
536 | (1) |
|
|
537 | (22) |
|
Analyzing Publications Jumpstart |
|
|
537 | (1) |
|
|
538 | (14) |
|
|
539 | (2) |
|
|
541 | (1) |
|
|
542 | (1) |
|
|
543 | (2) |
|
|
545 | (1) |
|
|
546 | (1) |
|
|
546 | (1) |
|
Publications can be good or bad |
|
|
547 | (2) |
|
|
549 | (3) |
|
|
552 | (6) |
|
|
552 | (1) |
|
|
553 | (4) |
|
|
557 | (1) |
|
|
558 | (1) |
|
|
559 | (50) |
|
|
559 | (1) |
|
The Idea of a Content Model |
|
|
560 | (3) |
|
|
563 | (7) |
|
Components are like objects |
|
|
564 | (1) |
|
The basic unit of content management |
|
|
565 | (1) |
|
How do you divide content? |
|
|
566 | (2) |
|
|
568 | (1) |
|
Content has types and components |
|
|
569 | (1) |
|
Content Types Have Elements |
|
|
570 | (3) |
|
Elements have types and values |
|
|
571 | (1) |
|
|
572 | (1) |
|
|
572 | (1) |
|
What Do Components Look Like? |
|
|
573 | (3) |
|
|
573 | (1) |
|
Components in structured files |
|
|
574 | (1) |
|
Components in relational databases |
|
|
575 | (1) |
|
Components in object databases |
|
|
575 | (1) |
|
The Relationship between Functionality and Components |
|
|
576 | (5) |
|
A functionality component |
|
|
577 | (3) |
|
Functionality content types and components |
|
|
580 | (1) |
|
|
581 | (9) |
|
|
582 | (1) |
|
|
582 | (7) |
|
|
589 | (1) |
|
A Sample Set of Content Types |
|
|
590 | (18) |
|
|
592 | (1) |
|
|
593 | (1) |
|
|
593 | (1) |
|
|
594 | (1) |
|
|
595 | (1) |
|
|
596 | (1) |
|
|
596 | (1) |
|
|
597 | (1) |
|
|
598 | (1) |
|
|
599 | (1) |
|
|
600 | (1) |
|
|
601 | (1) |
|
|
601 | (1) |
|
|
602 | (1) |
|
|
603 | (1) |
|
|
604 | (1) |
|
|
604 | (1) |
|
Standard management elements |
|
|
605 | (3) |
|
|
608 | (1) |
|
|
609 | (20) |
|
|
609 | (1) |
|
|
610 | (3) |
|
Who can become an author? |
|
|
611 | (1) |
|
Harvesting creative product |
|
|
611 | (1) |
|
|
612 | (1) |
|
Authoring prior to the CMS |
|
|
612 | (1) |
|
|
613 | (2) |
|
|
613 | (2) |
|
|
615 | (1) |
|
Your Attitude Toward Authors |
|
|
615 | (6) |
|
|
616 | (2) |
|
|
618 | (1) |
|
|
618 | (1) |
|
|
619 | (2) |
|
|
621 | (6) |
|
|
621 | (1) |
|
|
621 | (6) |
|
|
627 | (1) |
|
|
627 | (2) |
|
Accounting for Acquisition Sources |
|
|
629 | (18) |
|
|
629 | (2) |
|
|
631 | (6) |
|
|
631 | (1) |
|
|
632 | (3) |
|
|
635 | (1) |
|
|
635 | (2) |
|
Is It an Author or an Acquisition Source? |
|
|
637 | (1) |
|
|
638 | (7) |
|
|
638 | (1) |
|
|
639 | (6) |
|
|
645 | (1) |
|
|
645 | (2) |
|
Designing Content Access Structures |
|
|
647 | (36) |
|
Access Structure Jumpstart |
|
|
647 | (3) |
|
Understanding Access Structures |
|
|
650 | (19) |
|
Publication navigation versus CMS access structure |
|
|
652 | (1) |
|
|
653 | (3) |
|
|
656 | (3) |
|
|
659 | (3) |
|
|
662 | (4) |
|
|
666 | (2) |
|
|
668 | (1) |
|
Analyzing Access Structures |
|
|
669 | (12) |
|
|
669 | (1) |
|
|
670 | (10) |
|
|
680 | (1) |
|
|
681 | (2) |
|
|
683 | (50) |
|
|
683 | (1) |
|
Publications and Templates |
|
|
684 | (23) |
|
|
685 | (2) |
|
Mixing the static and the dynamic |
|
|
687 | (2) |
|
|
689 | (1) |
|
Creating a system of publications |
|
|
689 | (1) |
|
Using a template processor |
|
|
690 | (1) |
|
Understanding template logic |
|
|
691 | (1) |
|
Using templates within templates |
|
|
692 | (3) |
|
|
695 | (8) |
|
|
703 | (3) |
|
|
706 | (1) |
|
|
707 | (1) |
|
|
707 | (8) |
|
|
707 | (1) |
|
|
708 | (7) |
|
|
715 | (1) |
|
A Sample Set of Templates |
|
|
715 | (16) |
|
|
717 | (6) |
|
|
723 | (8) |
|
|
731 | (2) |
|
Designing Personalization |
|
|
733 | (22) |
|
Personalization Jumpstart |
|
|
733 | (1) |
|
Publications and Personalization |
|
|
734 | (8) |
|
Personalization and the audience |
|
|
734 | (2) |
|
Personalization and components |
|
|
736 | (1) |
|
Personalization and rules |
|
|
737 | (1) |
|
Personalizations in templates |
|
|
738 | (2) |
|
Customization versus personalization |
|
|
740 | (2) |
|
Dynamic and static personalization |
|
|
742 | (1) |
|
Analyzing Personalization |
|
|
742 | (11) |
|
|
743 | (1) |
|
|
743 | (9) |
|
|
752 | (1) |
|
|
753 | (2) |
|
Designing Workflow and Staffing Models |
|
|
755 | (36) |
|
|
755 | (2) |
|
|
757 | (9) |
|
|
761 | (1) |
|
|
762 | (2) |
|
A perspective on workflow |
|
|
764 | (1) |
|
|
765 | (1) |
|
Introducing Tasks, Jobs, and Steps |
|
|
766 | (7) |
|
|
767 | (1) |
|
|
768 | (2) |
|
|
770 | (1) |
|
|
771 | (1) |
|
|
772 | (1) |
|
Fitting Localization into Your Workflow |
|
|
773 | (4) |
|
|
777 | (7) |
|
|
777 | (1) |
|
|
778 | (6) |
|
|
784 | (1) |
|
|
784 | (4) |
|
|
785 | (1) |
|
|
785 | (3) |
|
|
788 | (1) |
|
|
788 | (3) |
|
|
791 | (270) |
|
|
793 | (12) |
|
|
793 | (1) |
|
Physical Design Essentials |
|
|
794 | (2) |
|
A Simple Physical Design Process |
|
|
796 | (2) |
|
Introducing the Technology Taxonomy |
|
|
798 | (5) |
|
An index to the technology taxonomy |
|
|
799 | (4) |
|
|
803 | (2) |
|
What Are Content Markup Languages? |
|
|
805 | (16) |
|
A Brief and Selective History of Markup Languages |
|
|
805 | (3) |
|
What Is a Markup Language? |
|
|
808 | (1) |
|
A Taxonomy of Markup Languages |
|
|
809 | (3) |
|
|
809 | (1) |
|
|
810 | (1) |
|
Extendable versus nonextendable |
|
|
811 | (1) |
|
|
812 | (1) |
|
|
812 | (6) |
|
Don't be baffled by syntax |
|
|
812 | (2) |
|
The language versus the interpreter |
|
|
814 | (1) |
|
Representing representation |
|
|
815 | (1) |
|
|
815 | (1) |
|
The benefits of white space |
|
|
816 | (2) |
|
People play in the margins |
|
|
818 | (1) |
|
|
818 | (3) |
|
XML and Content Management |
|
|
821 | (24) |
|
|
821 | (9) |
|
|
822 | (1) |
|
|
822 | (5) |
|
Management by Schema or DTD |
|
|
827 | (1) |
|
|
828 | (2) |
|
Using XML in Content Management |
|
|
830 | (4) |
|
|
830 | (1) |
|
|
830 | (1) |
|
|
831 | (1) |
|
|
832 | (1) |
|
Help from the rest of the XML gang |
|
|
832 | (2) |
|
|
834 | (9) |
|
|
835 | (1) |
|
Introducing DOM XML programming |
|
|
836 | (7) |
|
|
843 | (2) |
|
|
845 | (22) |
|
What Is Content Processing? |
|
|
845 | (3) |
|
|
846 | (1) |
|
|
847 | (1) |
|
Content Processing and the CMS |
|
|
848 | (7) |
|
Focusing on the long-term benefits |
|
|
848 | (3) |
|
Focusing on the short-term benefits |
|
|
851 | (1) |
|
Distilling the essence of a process |
|
|
852 | (1) |
|
Bringing people into processing |
|
|
852 | (1) |
|
|
853 | (2) |
|
Managing the Processing Project |
|
|
855 | (3) |
|
Taking stock of the content inventory |
|
|
856 | (1) |
|
Drafting the processing specification |
|
|
856 | (1) |
|
|
857 | (1) |
|
Getting to the Core of Content Mechanics |
|
|
858 | (7) |
|
Understanding the principles of mapping content |
|
|
860 | (5) |
|
|
865 | (2) |
|
Building Collection Systems |
|
|
867 | (50) |
|
|
868 | (1) |
|
Minimize Disruption, Maximize Specific Value |
|
|
868 | (1) |
|
Forms, Files, and Batch Processes |
|
|
869 | (1) |
|
Driven by a Content Model |
|
|
870 | (1) |
|
|
871 | (16) |
|
|
872 | (1) |
|
|
873 | (1) |
|
|
873 | (1) |
|
|
873 | (1) |
|
|
874 | (1) |
|
|
874 | (1) |
|
Integrated editorial and metatorial guides |
|
|
875 | (1) |
|
Off-line content creation |
|
|
876 | (1) |
|
|
876 | (1) |
|
|
877 | (1) |
|
|
878 | (3) |
|
|
881 | (3) |
|
Other authoring applications |
|
|
884 | (3) |
|
|
887 | (9) |
|
|
889 | (1) |
|
Mapping files to content types |
|
|
889 | (1) |
|
|
890 | (1) |
|
Integration with the aggregation system |
|
|
890 | (1) |
|
|
890 | (2) |
|
Quality control (QC) and monitoring |
|
|
892 | (2) |
|
|
894 | (2) |
|
|
896 | (6) |
|
Process and partner management |
|
|
897 | (1) |
|
|
897 | (1) |
|
|
898 | (1) |
|
Acquiring database records |
|
|
898 | (2) |
|
Acquiring Web site content |
|
|
900 | (2) |
|
|
902 | (12) |
|
Automatically applied metadata |
|
|
903 | (1) |
|
Metadata standards support |
|
|
904 | (1) |
|
|
904 | (1) |
|
|
905 | (1) |
|
|
906 | (3) |
|
|
909 | (5) |
|
|
914 | (1) |
|
|
914 | (1) |
|
Submitting and storing files |
|
|
914 | (1) |
|
|
915 | (1) |
|
|
915 | (2) |
|
Building Management Systems |
|
|
917 | (76) |
|
What's in a Management System? |
|
|
918 | (1) |
|
|
918 | (35) |
|
Fitting into the CMS and the organization |
|
|
919 | (1) |
|
Getting content in and out |
|
|
920 | (1) |
|
|
920 | (1) |
|
Global search and replace |
|
|
921 | (1) |
|
|
922 | (1) |
|
|
923 | (1) |
|
|
923 | (1) |
|
General storage requirements |
|
|
924 | (2) |
|
Relational database systems |
|
|
926 | (16) |
|
|
942 | (9) |
|
|
951 | (2) |
|
|
953 | (3) |
|
Automatic versus manual versioning |
|
|
954 | (1) |
|
|
954 | (1) |
|
|
955 | (1) |
|
|
955 | (1) |
|
|
956 | (1) |
|
Source Control System (Content and File Sharing) |
|
|
956 | (3) |
|
|
957 | (1) |
|
|
957 | (1) |
|
|
958 | (1) |
|
|
958 | (1) |
|
|
959 | (1) |
|
|
959 | (9) |
|
|
960 | (2) |
|
|
962 | (4) |
|
|
966 | (2) |
|
|
968 | (8) |
|
|
969 | (3) |
|
|
972 | (2) |
|
|
974 | (2) |
|
CMS Administration System |
|
|
976 | (14) |
|
|
977 | (1) |
|
|
978 | (1) |
|
|
978 | (1) |
|
|
979 | (1) |
|
|
980 | (2) |
|
|
982 | (1) |
|
|
982 | (1) |
|
Intellectual property tracking and costing |
|
|
983 | (1) |
|
|
984 | (3) |
|
|
987 | (3) |
|
|
990 | (3) |
|
Building Publishing Systems |
|
|
993 | (68) |
|
|
994 | (23) |
|
|
995 | (1) |
|
Producing target units structure |
|
|
996 | (1) |
|
|
996 | (1) |
|
|
997 | (3) |
|
Producing static and dynamic publications |
|
|
1000 | (1) |
|
On-the-fly conversion of text and media |
|
|
1001 | (1) |
|
Integration with publication authoring tools |
|
|
1002 | (1) |
|
|
1002 | (1) |
|
|
1003 | (14) |
|
|
1017 | (10) |
|
A personalization dashboard |
|
|
1017 | (1) |
|
|
1018 | (3) |
|
|
1021 | (3) |
|
|
1024 | (3) |
|
|
1027 | (3) |
|
|
1027 | (1) |
|
|
1028 | (1) |
|
|
1028 | (1) |
|
|
1029 | (1) |
|
|
1030 | (7) |
|
Integration with an existing Web infrastructure |
|
|
1030 | (2) |
|
|
1032 | (2) |
|
|
1034 | (1) |
|
Distributing files across servers |
|
|
1034 | (1) |
|
|
1035 | (2) |
|
|
1037 | (11) |
|
|
1037 | (2) |
|
Section and subsection support |
|
|
1039 | (1) |
|
|
1040 | (4) |
|
|
1044 | (1) |
|
Dynamic print publications |
|
|
1045 | (1) |
|
|
1045 | (3) |
|
|
1048 | (4) |
|
|
1049 | (1) |
|
|
1050 | (1) |
|
Integration to an e-mail server |
|
|
1050 | (1) |
|
|
1051 | (1) |
|
|
1051 | (1) |
|
|
1052 | (4) |
|
Syndication subscriber management |
|
|
1053 | (1) |
|
|
1054 | (1) |
|
Building and distributing feeds |
|
|
1055 | (1) |
|
Other Publication Systems |
|
|
1056 | (2) |
|
|
1058 | (1) |
|
|
1058 | (1) |
|
File and directory creation |
|
|
1058 | (1) |
|
Runtime dependency resolution |
|
|
1059 | (1) |
|
Database and metadata output |
|
|
1059 | (1) |
|
|
1059 | (2) |
Appendix: Epilogue |
|
1061 | (4) |
Index |
|
1065 | |