Often Web pages are produced dynamically by software running on the Web server, and represent the state of a changing database underneath it.ĭealing with these issues is the topic of much active research.However, later on, when another user tries to view that HTML, their browser might not be able to retrieve the included image since it may have been removed from the external server. When the submitter views the HTML in DSpace, their browser is able to use the reference in the HTML to retrieve the appropriate image, and so to the submitter, the whole HTML document appears to have been deposited correctly. For example, the HTML document may include an image from an external Web site, or even their local hard drive. This problem can manifest when a submitter uploads some HTML content. Thus, in a few year's time, when someone views the preserved Web site, they will probably find that many links are now broken or refer to other sites than are now out of context.In fact, it may be unclear to an end-user when they are viewing content stored in DSpace and when they are seeing content included from another site, or have navigated to a page that is not stored in DSpace. Web pages also link to or include content from other sites, often imperceptibly to the end-user.Web pages tend to consist of several files – one or more HTML files that contain references to each other, and stylesheets and image files that are referenced by the HTML files.HTML documents (Web sites and Web pages) are far more complicated, and this has important ramifications when it comes to digital preservation: This is fine for the majority of commonly-used file formats – for example PDFs, Microsoft Word documents, spreadsheets and so forth. For the most part, at present DSpace simply supports uploading and downloading of bitstreams as-is.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |