سیستم مدیریت منابع الکترونیکی ابتکاری : توسعه ی مشارکتی
|کد مقاله||سال انتشار||تعداد صفحات مقاله انگلیسی||ترجمه فارسی|
|10410||2004||7 صفحه PDF||سفارش دهید|
نسخه انگلیسی مقاله همین الان قابل دانلود است.
هزینه ترجمه مقاله بر اساس تعداد کلمات مقاله انگلیسی محاسبه می شود.
این مقاله تقریباً شامل 2951 کلمه می باشد.
هزینه ترجمه مقاله توسط مترجمان با تجربه، طبق جدول زیر محاسبه می شود:
- تولید محتوا با مقالات ISI برای سایت یا وبلاگ شما
- تولید محتوا با مقالات ISI برای کتاب شما
- تولید محتوا با مقالات ISI برای نشریه یا رسانه شما
پیشنهاد می کنیم کیفیت محتوای سایت خود را با استفاده از منابع علمی، افزایش دهید.
Publisher : Elsevier - Science Direct (الزویر - ساینس دایرکت)
Journal : Serials Review, Volume 30, Issue 2, 2004, Pages 110–116
نتیجه گیری انگلیسی
Innovative incorporated a number of new features into the ERM module. These features were grounded in the input provided by Innovative's development partners including workshops, scenario, and requirements documents. The workshops and scenario documents made it clear that representing the umbrella “electronic resource” was the most fundamental challenge to the architecture of the system. The “electronic resource,” particularly in its aggregation and full-text database manifestation, resembled the membership problem that libraries have struggled with for many years; however, it was more complex since relationships to licenses, payments, contacts, and in some cases thousands of aggregated titles needed to be addressed. Innovative solved this problem by enhancing its architecture to include new structures to describe the umbrella “electronic resource” and relate it to the appropriate license(s), payments, holdings, and contacts. Other requirements provided by the development partners directed Innovative to develop features such as automatic e-mail notification for critical resource management events like license expiration and renewal, new fixed and variable field structures, field level passwording, public display of rights and responsibilities, public display of “system down” messages, and several others. Throughout this part of the process, focus remained on satisfying the needs of the acquisition and supporting workflow described in the scenario and requirements documents provided by the development partners.