CORE Cost of Resource Exchange SMARTech Home资源交换的核心成本该回家了.pptVIP

下载本文档

0
0
约1.08万字
约 24页
2016-12-30 发布于上海
举报
版权申诉

CORE Cost of Resource Exchange SMARTech Home资源交换的核心成本该回家了.ppt

1、本文档共24页，可阅读全部内容。
2、原创力文档（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。
3、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
5、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
6、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
7、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
8、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

Once there’s a standard The data exchangers have to implement And test And deliver, document, support Which is where the user community (you!) comes in * * My involvement in this standard was begun as SirsiDynix developed a business partnership with Serials Solutions to provide for us and allow us to sell their ERMS. In our initial meetings, we talked about the necessity to pull ERM cost information from the ILS Acq. system into the ERAMS. We were then approached by ExLibris, desiring to pull information into VERDE from Unicorn. In or around there, I was contacted by Norm Medeiros, whose committee was also attempting to identify those elements most likely to populate the ERMS from an ILS Acq. system. 12/14/2006 – Interview with ERMI II group * This subcommittee had pulled together their own institutional requirements for populating an ERMS with ILS Acquisitions data. They also polled ERMS and ILS product managers and librarians and created a whitepaper with their findings. * Ted analyzed the white paper for the elements most frequently or less frequently requested. Narrowed the number of elements to 10. We then talked to other vendors to discover what they would expect to send from or receive in their systems. We asked specific questions of the ERMI II Subcommittee and of others to tighten up the terminology/data elements. We recognize that a set of data elements which is well defined, clear and simple, will increase the likelihood of adoption. * We settled on 24 basic elements for the initial CORE standard. * There were other elements that we ruled out for various reasons, mostly relevancy to the ERAMS. * Here are the basic application Use Cases we thought of, but we recognize there may be others. As various stake-holders join the working group, we believe they will help us settle on some Use Cases which help drive both the data elements and their transport mechanism. * Once these Use Cases are developed, they will help us know if we are missing any data eleme