Pengurusan aset digital
Pengurusan aset digital merupakan satu kaedah melindungi bahan digital sepeti filem dan buku eletronik. Pengurusan aset digital memerlukan pengekalan pemilikan objek didigitalkan yang tidak terputus sementara membenarkan capaian bagi mereka yang telah diberikan hak tersebut. Sebaik sahaja objek media memasuki domain digital, pemiliknya boleh mengawal siapakah yang boleh melihat, menggunakan, atau mengubah suai aset itu dan melaksanakan kawalan tersebut melalui penggunaan beberapa kaedah penyulitan yang digunakan untuk menguatkuasaan hak digital. Aplikasi yang melaksanakan pengurusan aset digital (digital rights management - DRM) mengenakan kaedah pengurusan hak digital ( DRM ) mereka apabila objek digital baru dibawa di bawah pengurusan, sama ada dengan mengimportnya dari domain analog dan / atau mendigitalkannya (dengan pengimbasan, pengecaman aksara optik, dll.) atau mengarangnya sebagai objek baru. Objek digital yang tidak menggunakan DRM tidak boleh dibawa ke DAM, tetapi boleh diuruskan dalam sistem pengurusan kandungan.
Pengindeksan objek yang wujud hanya dalam bentuk analog (dokumen bercetak atau gambar di atas kertas misalnya) kedalam sistem digital (iaitu pangkalan data dalam talian bagi karya yang diterbitkan) bukanlah DAM kerana objek data bentuk binary yang dikodkan perlu ada sebelum DRM dapat dilaksanakan sebelum ia boleh diimport oleh aplikasi DAM.
Bagi sesuatu objek yang berada di bawah kawalannya, sistem DAM boleh menawarkan kemudahan untuk menjelasan, pengkatalogan, capaian semula dan pengedarannya.
Istilah "pengurusan aset media" (MAM) boleh digunakan sebagai rujukan pada DAM yang digunakan untuk sub-set objek digital yang lazimnya dianggap "media", iaitu rakaman audio, foto dan video.
 | Tolong bantu menterjemahkan sebahagian rencana ini. Rencana ini memerlukan kemaskini dalam Bahasa Melayu piawai Dewan Bahasa dan Pustaka. Sila membantu, bahan-bahan boleh didapati di Pengurusan aset digital (Inggeris). Jika anda ingin menilai rencana ini, anda mungkin mahu menyemak di terjemahan Google. Walau bagaimanapun, jangan menambah terjemahan automatik kepada rencana, kerana ini biasanya mempunyai kualiti yang sangat teruk. Sumber-sumber bantuan: Pusat Rujukan Persuratan Melayu. |
The more-recent[bila?] concept of enterprise content management (ECM) often deals with solutions which address similar features but in a wider range of industries or applications.[1]
Smaller DAM systems are easier to categorize as to content and usage since they normally operate in a particular operational context. This would hold true for systems attached to audio- or video-production systems. The key differentiators here are the types of decoders and I/O (input/output) used for the asset ingest, use and outgest. Since metadata describes the essence (and proxy copies), the metadata can serve as a guide to the playout decoders, transcoders, and channels as well as an input to access-control rules. This means that the essence can be treated as a non-described storage object except when being accessed for viewing or editing. There is relevance to this when considering the overall design and use of larger implementations.[perlu rujukan] The closer the asset is to the ingest/edit/playout tool, the greater the technical architecture needs to accommodate delivery requirements such as bandwidth, latency, capacity, access control, availability of resources, etc. The further the asset moves into a general storage architecture (e.g. hierarchical storage management [HSM]) the more it can be treated as a general blob (binary large object) that is typically held in a filesystem, not in a database. The impact of this set of needs means that it is possible and reasonable to design larger systems using smaller, more expensive performance-systems at the edge of the network where the essence is being used in its intended form and less expensive systems further back for storage and archival. This type of design exemplifies Infrastructure Convergence Architecture, where the line-of-business operations technology and IT technologies depend on one another for functional and performance (non-functional) requirements.
Assets
[sunting | sunting sumber]There is usually a target version – referred to as "essence" – generally the highest-resolution and highest-fidelity representation. The asset is detailed by its metadata. Metadata is the description of the asset and the description depth can vary depending on the needs of the system, designer, or user. Metadata can describe, but is not limited to, the description of: asset content (what is in the package?); the means of encoding/decoding (e.g. JPEG, tar, MPEG 2); provenance (history to point of capture); ownership; rights of access; as well as many others. There exist some predefined standards and template for metadata such as Dublin Core and PBCore. In cases of systems that contain large-size asset essences, such as MPEG 2 and JPEG2000 for the cases of images and video, there are usually related "proxy" copies of the essence. A proxy copy is a lower-resolution representation of the essence that can be used as a reference in order to reduce the overall bandwidth requirements of the DAM system infrastructure. It can be generated and retained at the time of ingestion of the asset simultaneous or subsequent to the essence, or it can be generated on the fly using transcoders.
Types of systems
[sunting | sunting sumber]The following broad categories of digital asset management systems may be distinguished as:[perlu rujukan]
- Brand asset management systems, with a focus on facilitation of content re-use within large organizations. Here the content is largely marketing- or sales-related, for example, product imagery, logos, marketing collateral or fonts, to give a few examples.
- Library asset management systems, with a focus on storage and retrieval of large amounts of infrequently changing media assets, for example in video or photo archiving.
- Production asset management systems focus on managing assets as they are being created for a digital media production (video game, 3D feature film, animation, visual-effects shots, etc.) They usually include work-flow and project-management features coupled with the storage, organization and revision control of frequently changing digital assets.
DAM software may be open source or proprietary.
Rujukan
[sunting | sunting sumber]- ^ Magan Arthur (30 April 2005), Intro to Digital Asset Management: Just what is a DAM?, diarkibkan daripada yang asal pada 22 July 2012
Bacaan lanjut
[sunting | sunting sumber]- Diamond, David (2012). DAM Survival Guide: Digital Asset Management Initiative Planning. DAMSurvivalGuide.com.
- Krogh, Peter (2009). The DAM Book, Second Edition. O'Reilly Media. ISBN 0-596-52357-2.
- Krogh, Peter (2005). The DAM Book: Digital Asset Management for Photographers. O'Reilly Media. ISBN 0-596-10018-3.
- Austerberry, David (2006). Digital Asset Management, Second Edition. Focal Press. ISBN 0-240-80868-1.
- Jacobsen, Jens; Schlenker, Tilman; Edwards, Lisa (2005). Implementing a Digital Asset Management System: For Animation, Computer Games, and Web Development. Focal Press. ISBN 0-240-80665-4.
- Mauthe, Andreas; Thomas, Peter (2004). Professional Content Management Systems: Handling Digital Media Assets. Wiley. ISBN 0-470-85542-8.
Pautan luar
[sunting | sunting sumber]- Digital Asset Management and Museums – Digital Asset Management and Museums – An Introduction.
- List of Digital Asset Management Vendors – Comprehensive list of DAM vendors.
- Open Source Digital Asset Management – Overview of Open Source DAM systems.
- DAM Directory – Actively maintained directory of DAM-related resources.