SUNScholar/Interoperability
Jump to navigation
Jump to search
Back to Guidelines
Contents
Definition
As per wikipedia (2016/05/09);
"Interoperability is a property of a product or system, whose interfaces are completely understood, to work with other products or systems, present or future, without implementation or any restrictions in access. While the term was initially defined for information technology or systems engineering services to allow for information exchange, a more broad definition takes into account social, political, and organizational factors that impact system to system performance."
Interfaces
What "interfaces" does DSpace have?
Input
Using User Interfaces
- Submit content using the XMLUI interface.
- Import content using the XMLUI administrative interface.
- Import metadata using the XMLUI administrative interface.
Using System Interfaces
- Submit content using the web API.
- Import using the packages format.
- Import using the simple archive format.
- Backup using the AIP format.
- Archive content in the cloud.
- Submit items using the SWORD interface.
- Harvest the content of remote collections to the local IR via the OAI interface.
Output
Using User Interfaces
- Download content using the XMLUI interface.
- Export content using the XMLUI administrative interface.
- Export metadata using the XMLUI administrative interface.
Using System Interfaces
- Allow other systems to modify content using the web API.
- Export using the packages format.
- Export using the simple archive format.
- Restore using the AIP format.
- Restore archived content from the cloud.
- Allow remote systems to "harvest" the content of the local IR via the OAI interface.
SAFBuilder
- Click on the heading above
Conclusion
DSpace has many interfaces that allow for content interoperability with other systems.
In addition DSpace is built using open systems to allow for technical interoperability with other open systems.