DOCSLIB.ORG

Clearcase Environment How Do I Web Page

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Clearcase Environment How Do I Web Page ClearCase Environment – How do I Soft - is your software and documentation Asset - is something that must be protected Management - is what we do Enterprise - is the capability Computing - is the power Services - are what we provide ClearCase Environment – “How do I”:(Last update 12-Dec-12) Anti-virus software and ClearCase – recommendations, etc... Server processes – lockmgr (redundancy in v7) & new vob_almd_params file, stopping and starting (windows & remotely), etc... ClearCase Registry – commands requiring the registry password, etc... Multi Version File System (MVFS) layer – understanding, debugging, flushing the cache, etc... LDAP and Active Directory services – issues, etc... Shell access – understanding, etc... Network Attached Storage devices - root permissions and, chown_pool & chown_container, etc... Storage – default location for Views on windows, etc... .NET issues – understanding etc,... Regions – Tags, etc... Email – configuring, etc... Problems and Issues - “The Evil twins” , eclipsed files, protectvob and, etc... Installation and patching of ClearCase - including silent install, patching, uninstalling, feature differences ClearCase and ClearCase LT etc... Firewalls – ClearCase and etc... Upgrading and compatibility issues between major versions, preserving installs, etc... Plugins & integrations for ClearCase - Eclipse, ClearCase Automation Libraty (CAL), Source Code Control provider (changing), etc... ClearCase context menus – configuring etc... Temporary files – created by and used by ClearCase, etc... Virtualisation – support policy Interop environment between Windows and UNIX – usernames & groups, VOB & View creation in, SaMBa configuration, issues, CLEARCASE_GROUPS, etc... Licensing – commands that don’t take a license, etc... Permissions executables and 770 directories, Support policies – Linux, DFS, Alteris, etc Caching – ClearCase cache directory, etc... ClearCase environment – firewalls, . (dot) files, temporary files, services, magic files, ASP .net framework, name conventions, clearmenuadmin, cache files, encryption software,etc... ClearCase scheduler – using without NIS, groups and, etc... Anti-virus software and ClearCase – recommendations, etc... Page 1 of 341 ClearCase Environment – How do I Table of contents CLEARCASE ENVIRONMENT – “HOW DO I”:(LAST UPDATE 12-DEC-12) .................... 1 TABLE OF CONTENTS ................................................................................................................................ 2 ANTI-VIRUS SOFTWARE ........................................................................................................................ 12 1. How do I – understand the support Policy for Anti-Virus software and ClearCase ................................................................................................................................................. 12 RELATED INFORMATION ........................................................................................................................ 13 2. How do I – understand the RPC: Remote system error - [WINSOCK] No buffer space available issue .............................................................................................................. 13 SERVER PROCESSES ............................................................................................................................... 14 3. How do I – understand about the albd_rt_params.conf file .................................. 14 4. How do I – understand about Rational ClearCase server processes .................. 15 MultiVersion File System MVFS (MultiVersion File System) is not a server process, it loads a kernel driver that presents a file system to the user through a standard interface; see technote 1230196. .................................................................................................. 16 5. How do I – understand the Lock Manager process post and pre ClearCase v7 16 6. How do I - monitor the Lock Manager status on Windows ..................................... 18 7. How do I - Monitor the Lock Manager status on UNIX and Linux ........................ 20 8. How do I - diagnosing Lock Manager registry settings on Windows .................. 20 9. How do I – understand about the db.conf configuration file ................................. 21 10. How do I – understand about deadman lock time-outs .......................................... 21 11. How do I – resolve a this client was launched with different lockmgr parameters than those now in the almd file issue ................................................................... 22 12. How do I - start and stop ClearCase from the Windows command line ............ 22 13. How do I - starting and stopping ClearCase services remotely ............................ 23 14. How do I – understand the unable to contact albd_server issue ........................ 23 15. How do I – understand how ALBD RPC calls can cause significant performance degradation under very high load ........................................................................ 23 16. How do I – understand why Rational ClearCase operations hang with the error message of "timed out trying to communicate with ClearCase remote server. " 23 SYMPTOM ................................................................................................................................................. 23 CAUSE ...................................................................................................................................................... 24 ENVIRONMENT ........................................................................................................................................ 24 RESOLVING THE PROBLEM .................................................................................................................... 25 17. How do I – understand about RPC services and ClearCase on UNIX and Linux 25 CLEARCASE REGISTRY .......................................................................................................................... 26 18. How do I - manually restoring the primary registry server files from backup 26 19. How do I – get a non-root UNIX account to run rgy_passwd ............................... 28 20. How do I – understand the ClearCase commands that require a ClearCase registry password ................................................................................................................................. 28 21. How do I – deal with the ClearCase 7.0.1 registry files on UNIX and Linux hosts moving from 'rgy' directory to the 'config' directory................................................... 29 22. How do I - set or change the ClearCase registry password ................................... 30 23. How do I – understand how a non-root UNIX account can run rgy_passwd... 30 24. How do I – understand the computer is not a valid registry server problem . 31 25. How do I - Improve lsview -host and lsvob -host performance ........................... 32 MVFS ...................................................................................................................................................... 33 26. How do I – understand why the ClearCase start script prevents MVFS from being unloaded from kernel under some conditions ............................................................... 33 Page 2 of 341 ClearCase Environment – How do I 27. How do I – understand about the MVFS cache values in ClearCase Control Panel and cleartool getcache ............................................................................................................ 34 28. How do I – why the iInstallation of ClearCase 7.1 fails during post-install phase and logs MVFS errors: Trouble mounting the viewroot "/view" ............................ 36 29. How do I – understand why you are unable to load MVFS on UNIX or Linux after install .............................................................................................................................................. 37 30. How do I – understand why a ClearCase installation on Linux x86 fails because MVFS cannot be loaded. ................................................................................................... 37 31. How do I – understand about the MultiVersion File System (MVFS) .................. 38 32. How do I – run MVFS Debugging ..................................................................................... 38 33. How do I – understand about cleartext lookup and flushing the mvfscache .. 39 34. How do I – understand the MVFS Scaling Factor on Windows ............................. 40 35. How do I – Understand the invalid MSDOS Function error on Windows copying a file from a UNIX or Linux VOB ..................................................................................... 42 36. How do I - install or uninstall the MVFS on Windows ............................................... 43 37. How do I – known the limitations for the MVFS on Microsoft Windows ............ 44 38. How do I - rebuild the mvfs module for use with ClearCase 7.0.x ..................... 44 39. How do I – understand why Rebuilding of MVFS modules with kernel symbol exports fails but installation of ClearCase is successful ......................................................... 44 40. How do I – configure the MVFS settings for use with eclipse based Rational products and dynamic views ............................................................................................................ 45 LDAP &
Load more

Recommended publications
  • APPLICATION of the DELTA DEBUGGING ALGORITHM to FINE-GRAINED AUTOMATED LOCALIZATION of REGRESSION FAULTS in JAVA PROGRAMS Master’S Thesis
    TALLINN UNIVERSITY OF TECHNOLOGY Faculty of Information Technology Marina Nekrassova 153070IAPM APPLICATION OF THE DELTA DEBUGGING ALGORITHM TO FINE-GRAINED AUTOMATED LOCALIZATION OF REGRESSION FAULTS IN JAVA PROGRAMS Master’s thesis Supervisor: Juhan Ernits PhD Tallinn 2018 TALLINNA TEHNIKAÜLIKOOL Infotehnoloogia teaduskond Marina Nekrassova 153070IAPM AUTOMATISEETITUD SILUMISE RAKENDAMINE VIGADE LOKALISEERIMISEKS JAVA RAKENDUSTES Magistritöö Juhendaja: Juhan Ernits PhD Tallinn 2018 Author’s declaration of originality I hereby certify that I am the sole author of this thesis. All the used materials, references to the literature and the work of others have been referred to. This thesis has not been presented for examination anywhere else. Author: Marina Nekrassova 08.01.2018 3 Abstract In software development, occasionally, in the course of software evolution, the functionality that previously worked as expected stops working. Such situation is typically denoted by the term regression. To detect regression faults as promptly as possible, many agile development teams rely nowadays on automated test suites and the practice of continuous integration (CI). Shortly after the faulty change is committed to the shared mainline, the CI build fails indicating the fact of code degradation. Once the regression fault is discovered, it needs to be localized and fixed in a timely manner. Fault localization remains mostly a manual process, but there have been attempts to automate it. One well-known technique for this purpose is delta debugging algorithm. It accepts as input a set of all changes between two program versions and a regression test that captures the fault, and outputs a minimized set containing only those changes that directly contribute to the fault (in other words, are failure-inducing).
    [Show full text]
  • Embedded Software Knowledge Management System (ESWKMS) Release 0.0
    Embedded Software Knowledge Management System (ESWKMS) Release 0.0 ESWKMS community September 24, 2015 Contents 1 Human Relation Patterns 3 1.1 Categorization of human relation patterns................................3 2 Build Patterns 5 2.1 Categorization of build patterns.....................................5 2.2 All build patterns in alphabetic order..................................6 3 Release Antipatterns 9 4 Requirement Patterns 11 4.1 Standardized Textual Specification Pattern............................... 11 4.2 Perform Manual Review Pattern..................................... 11 5 Design Patterns 13 5.1 Categorization of “design” patterns................................... 13 5.2 Pattern Selection Procedure....................................... 19 5.3 Legend to the design pattern sections.................................. 19 5.4 All design patterns in alphabetic order.................................. 19 6 Idioms in C 27 6.1 Classification of idioms......................................... 27 6.2 Add the name space........................................... 27 6.3 Constants to the left........................................... 27 6.4 Magic numbers as variables....................................... 28 6.5 Namend parameters........................................... 28 6.6 Sizeof to variables............................................ 28 7 Bibliography 29 8 “It is all about structure and vision.” 31 9 Indices and tables 33 i ii Embedded Software Knowledge Management System (ESWKMS), Release 0.0 Contents: Contents 1 Embedded
    [Show full text]
  • Red Hat Enterprise Linux 7 7.8 Release Notes
    Red Hat Enterprise Linux 7 7.8 Release Notes Release Notes for Red Hat Enterprise Linux 7.8 Last Updated: 2021-03-02 Red Hat Enterprise Linux 7 7.8 Release Notes Release Notes for Red Hat Enterprise Linux 7.8 Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Setting up Railpic] 12Th March 2020
    [Setting up RailPIC] 12th march 2020 1 Introduction This document provides a step by step guide to get a full DIY digital station for model trains running on an ARM device. The current development is based on my initial ideas to make rocrail (www.rocrail.net) run on a raspberry pi (www.raspberrypi.org/). The old document with such ideas – “Setting up rocpi v1.93” – is still available in the same repository where you have found this manual. Nowadays, the target HW used as basis for this project has shifted towards the odroid platform (http://www.hardkernel.com/main/main.php), specifically the C1 (C1+) board, thought all the instructions in this document are most probably equally suitable for the C2 board. The operating system used as basis has also shifted towards arch linux (https://archlinuxarm.org/), which in addition to be faster, more configurable and more updated than other tailored-made OS for other platforms – as Raspbian, it is available for multiple ARM devices. This allows to maintain this manual with detailed instructions both for odroid and raspberry pi (for testing purposes). The basic software to manage the trains layout is still rocrail, though, since the rpicd software emulates standard central stations, any other control software could be used too. The distribution of rpicd has also evolved towards the use of dockers (https://www.docker.com/) as main way to keep the software updated and independent on the HW and OS platform The final objective is to get the ARM device running on a very simple configuration, starting rocrail as a daemon, and enabling the launching of rocview through the activation of a digital input.
    [Show full text]
  • Case Sensitivity Versus Case Preservation in CIFS Server (Samba)
    Title: Case Sensitivity versus Case Preservation in CIFS Server (Samba) Author: Don McCall, Senior Support Engineer, Hewlett-Packard GSE Introduction The differences between PC and UNIX file systems are legion: how big they can be, what attributes they support, what characters are legal for file and directory names, etc. Samba does a truly heroic job of handling these differences. One way it does that is by recognizing and handling the difference between an operating system that is case sensitive (Unix), and one that simply preserves case (Microsoft Windows9x, WinNT, and Windows2000). In this article I'd like to examine this difference. Let us take for our study four filenames: FILEONE.TXT filetwo.txt Filethree.txt FiLeFoUr.TxT The first file (FILEONE.TXT) is all uppercase. The second file (filetwo.txt) is all lowercase. The third file is a special ‘case’ whose first letter ONLY is uppercase. The fourth file (FiLeFoUr.TxT) is a truly 'mixed' case, representative of the myriad case permutations a file name could take on. In Unix, if we used the touch command to create these four filenames, we would get exactly what we requested, i.e., a set of files in the directory whose names exactly matched the case we typed in, as we see here from the output of the UNIX ‘ll’ command: · rw-r-r-- 1 root sys 0 Dec 19 15:17 FILEONE.TXT · rw-r-r-- 1 root sys 0 Dec 19 15:18 FiLeFoUr.TxT · rw-r-r-- 1 root sys 0 Dec 19 15:18 Filethree.txt · rw-r-r-- 1 root sys 0 Dec 19 15:18 filetwo.txt Note that the Unix command 'll' doesn't alter this presentation – the filenames are shown just as they are represented in the file system.
    [Show full text]
  • Software Configuration Management
    Front cover Software Configuration Management A Clear Case for IBM Rational ClearCase and ClearQuest UCM Implementing ClearCase Implementing ClearQuest for UCM ClearCase and ClearQuest MultiSite Ueli Wahli Jennie Brown Matti Teinonen Leif Trulsson ibm.com/redbooks International Technical Support Organization Software Configuration Management A Clear Case for IBM Rational ClearCase and ClearQuest UCM December 2004 SG24-6399-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xvii. First Edition (December 2004) This edition applies to IBM Rational ClearCase and MultiSite Version 2003.06.00 and IBM Rational ClearQuest and MultiSite Version 2003.06.00. Some information about Version 06.13 is included. © Copyright International Business Machines Corporation 2004. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xvii Trademarks . xviii Preface . xix The team that wrote this redbook. xxi Become a published author . xxiii Comments welcome. xxiii Part 1. Introduction to SCM . 1 Chapter 1. The quest for software lifecycle management . 3 Stories from the wild. 4 Software asset management . 5 Better software configuration management means better business . 6 Seven keys to improving business value . 7 Safety . 7 Stability . 8 Control. 8 Auditability. 9 Reproducibility. 10 Traceability . 11 Scalability . 12 Good SCM is good business . 13 Chapter 2. Choosing the right SCM strategy . 15 The questions. 16 A version control strategy. 17 Delta versioning . 17 A configuration control strategy . 19 A process management strategy . 21 A problem tracking strategy . 23 Chapter 3. Why ClearCase and ClearQuest .
    [Show full text]
  • Soc Concurrent Development Page 1 of 7
    SoC drawer: SoC concurrent development Page 1 of 7 SoC drawer: SoC concurrent development Establish a disciplined process for hardware and software co -design, integration, and test Sam Siewert ( [email protected] ), Adjunct Professor, University of Colorado Summary: A system-on-a-chip (SoC) can be more complex in terms of hardware-software interfacing than many earlier embedded systems because an SoC often includes multiple processor cores and numerous I/ O interfaces. The process of integrating and testing the firmware-hardware interface can begin early, but without good management and testing, the mutability of firmware and early stages of hardware design simulation can lead to disastrous setbacks for a project. This article teaches system designers about tools and methods to minimize project churn. View more content in this series Date: 20 Dec 2005 Level: Intermediate Activity: 687 views Comments: 0 ( Add comments ) Average rating (based on 17 votes) This article is the third in the SoC drawer series . The series aims to provide the system architect with a starting point and some tips to make system-on-a-chip (SoC) design easier. SoCs are either configurable or reconfigurable. Configurable SoCs are constructed from core logic that can be reused and modified for an application-specific integrated circuit (ASIC) implementation; reconfigurable SoCs use soft cores and field-programmable gate array (FPGA) fabrics that can be reprogrammed by simply downloading new in-circuit FPGA programming. The mutability of SoCs in terms of firmware and FPGA fabric is attractive because it allows for modification and addition of features. Likewise, for configurable SoCs, the mutability during early co-design and co-simulation allows for quick design changes in both hardware and firmware, making for a very agile project.
    [Show full text]
  • MKS Toolkit UNIX to Windows Porting Guide
    MKS Toolkit UNIX to Windows Porting Guide MKS Inc. MKS Toolkit: UNIX to Windows Porting Guide ©2004 MKS Software Inc.; in Canada copyright owned by MKS Inc. All rights reserved. MKS, MKS Toolkit, and AlertCentre are registered trademarks of MKS Inc. NuTCRACKER is a registered trademark of MKS Software Inc. All other trademarks referenced are the property of their respective owners. MKS Inc. 12450 Fair Lakes Circle Suite 400 Fairfax, Virginia 22033 Phone: +1 703 803-3343 Fax: +1 703 803-3344 E-mail: [email protected] 8.7-0604 Technical Support To request customer support, please contact us by one of the means listed below and in your request include the name and version number of the product, your serial number, and the operating system and version/patch level that you are using. Contact MKS customer support at: Web: http://www.mkssoftware.com/support E-mail: [email protected] Telephone: +1-703-803-7660 (9:00am to 7:00pm Eastern, Mon-Fri) Fax: +1-703-803-3344 When reporting problems, please provide a test case and test procedure, if possible. If you are following up on a previously reported problem, please include the problem tracking number in your correspondence. Finally, tell us how we can contact you. Please give us your e-mail address and telephone number. UNIX to Windows Porting Guide iii iv MKS Toolkit Table of Contents 1 Introduction...............................................................1 A Note About Compilers ........................................................................2 2 Windows Concepts ..................................................3
    [Show full text]
  • An Application of Configuration Management on Graphical Models
    MBVC – Model Based Version Control: An Application of Configuration Management on Graphical Models MEHIAR MOUKBEL Master of Science Thesis Stockholm, Sweden 2007 i MBVC – Model Based Version Control: An Application of Configuration Management on Graphical Models By: Mehiar Moukbel A A B Merge Engine B Master of Science Thesis MMK 2007:38 MDA261 KTH Machine Design SE-10044STOCKHOLM ii Master of Science Thesis MMK 2007:38 MDA261 MBVC – Model Based Version Control: An Application of Configuration Management on Graphical Models Mehiar Moukbel Approved Examiner Supervisor 2007-03-20 Martin Törngren Jianlin Shi Jad El-Khoury Commissioner Contact person KTH, Machine Design Abstract File-based version control consists of tools in the software engineering industry, with many available commercial products that allow multiple developers to work simultaneously on a single project. However these tools are most commonly used on plain textual documents such as source code. There exist few tools today for versioning fine-grained data such as graphical Simulink models. Since Simulink is widely used as a modeling tool in numerous engineering fields, nonetheless in the mechatronics field, it will be interesting to study the possibility of developing a tool for version control of graphical models. Two textual software configuration management (SCM) products, CVS and Rational Clear Case, were studied and their functionalities were analyzed, along with a different number of research topics on document versioning. The existing algorithms of ‘diff’ and ‘merge’ functions were also studied to give an understanding of how these functions work for text based documents. The knowledge gained from the tools, existing algorithms and literature on the subject were used to write MATLAB programs that perform diff and merge on Simulink models.
    [Show full text]
  • Time to Re-Wire.Pdf
    Organised Sound http://journals.cambridge.org/OSO Additional services for Organised Sound: Email alerts: Click here Subscriptions: Click here Commercial reprints: Click here Terms of use : Click here Time to re­wire? Problems and strategies for the maintenance of live electronics RICHARD POLFREMAN, DAVID SHEPPARD and IAN DEARDEN Organised Sound / Volume 11 / Issue 03 / December 2006, pp 229 ­ 242 DOI: 10.1017/S1355771806001543, Published online: 17 November 2006 Link to this article: http://journals.cambridge.org/abstract_S1355771806001543 How to cite this article: RICHARD POLFREMAN, DAVID SHEPPARD and IAN DEARDEN (2006). Time to re­wire? Problems and strategies for the maintenance of live electronics. Organised Sound,11, pp 229­242 doi:10.1017/S1355771806001543 Request Permissions : Click here Downloaded from http://journals.cambridge.org/OSO, IP address: 132.216.227.42 on 20 Aug 2012 Time to re-wire? Problems and strategies for the maintenance of live electronics RICHARD POLFREMAN{, DAVID SHEPPARD{ and IAN DEARDEN{ {Music Department, University of Southampton, Southampton SO17 1BJ, UK E-mail: [email protected] {Sound Intermedia, 7 Ossian Mews, London N4 4DT, UK E-mail: [email protected], [email protected] While much work is proceeding with regard to the settings, audio, video, etc.), these have also introduced preservation and restoration of audio documents in general new problems, and in some cases may accelerate the and compositions for tape in particular, relatively little potential loss of works. First, digital media have research has been published with regard to the issues of reducedtheperceivedneedtorecordinformationsuch preserving compositions for live electronics. Such works often as synthesizer parameters on hard copy (paper).
    [Show full text]
  • Meeting the Challenge of Media Preservation: Strategies and Solutions August 2011
    Meeting the Challenge of Media Preservation: Strategies and Solutions August 2011 Meeting the Challenge of Media Preservation: Strategies and Solutions Indiana University Bloomington Media Preservation Initiative Task Force August 2011 Our history is at risk Indiana University Bloom- ington is home to at least 3 million sound and moving image recordings, photos, documents, and artifacts. Well over half a milion of these special holdings are part of audio, video, and film collections, and a large num- ber of them are one of a kind. These invaluable cultural and historical gems, and many more, may soon be lost. Forever. IMAGES, PREVIOUS PAGE: g The Archives of African g Gloria Gibson, Frances Stubbs, and founding director Phyllis American Music and Culture Klotman pose in 1985 with part of the Black Film Center/Archive’s has ninety-one audiocas- rich collection of films and related materials by and about African settes of interviews conducted Americans. Photo courtesy of the Black Film Center/Archive. by Michael Lydon with Ray Charles and his associates as background for the book Ray Charles: Man and Music. Image from IU News Room. g The Blackbird (1926), star- g Herman B Wells was an edu- g In 1947 Bill Garrett broke a ring Lon Chaney, is one of cational visionary who helped color barrier in major college many historically important transform Indiana University basketball by becoming the films found in the David S. into an internationally recog- first black player signed in Bradley Collection. Photo nized center of research and the Big Ten. He led the team courtesy of Lilly Library.
    [Show full text]
  • Masterarbeit
    Masterarbeit zur Erlangung des akademischen Grades Master Technische Hochschule Wildau Fachbereich Wirtschaft, Informatik, Recht Studiengang Bibliotheksinformatik M. Sc. Thema (deutsch): Preservation Planning für die digitalen audio-visuellen Materialen der Technischen Informationsbibliothek Hannover - Entwicklung eines Kriterienkataloges und eines Migration Plugins Thema (englisch): Preservation Planning for Digital Audio-Visual Material at the German National Library of Science and Technology (TIB) – Developing a Catalogue of Criteria and a Migration Plugin Autor/in: Merle Friedrich Matrikel-Nr.: 50041765 Seminargruppe: BIM/16 Betreuer/in: M. Eng. Marcel-Dominique Paul Block Zweitgutachter/in: Prof. Dr. rer. nat. Janett Mohnke Eingereicht am: 03.03.2019 Bibliographic Description Preservation Planning for Digital Audio-Visual Material at the German National Library of Science and Technology (TIB) – Developing a Catalogue of Criteria and a Migration Plugin Masterarbeit 2019, 81 Seiten, 12 Abbildungen; 15 Tabellen; 4 Anlagen Technische Hochschule Wildau, Fachbereich WIR Goal: Evaluation of the risk of obsolescence for the most common audio-visual file formats in TIB’s holdings and development of a migration plugin Inhalt: Die Technische Informationsbibliothek Hannover (TIB) betreibt ein Langzeitarchivie- rungssystem um die digitalen Bestände, unter anderem audiovisuelle Materialien, zu erhalten. Um obsolete audiovisuelle Formate zu identifizieren wird ein Kriterienkatalog entwickelt. Diejenigen Formate, welche einen Großteil der audiovisuellen
    [Show full text]