Skip to main content

OPEX Metadata for PUT

  • January 12, 2023
  • 8 replies
  • 1078 views

CX Team
Forum|alt.badge.img+4

Editions

Using PUT is included in Cloud Professional, Cloud Professional Plus, Enterprise Private Cloud (EPC), Enterprise Private Cloud Perform (EPCP) and Enterprise on Premise (EoP) editions.

The PUT tool is not relevant for Starter.

 

Preservica Versions

This document is valid from v6.6.1

 

Introduction

For everyone on Cloud and Enterprise editions using PUT we are introducing enhancements from v.6.6.1, planned for release in early 2023. These enhancements will give you the ability to ingest a file into a folder without the need for a containing folder, something that the community has been asking about for a long time.

The enhancements will enable Cloud and Enterprise users to take advantage of upcoming features, including uploading metadata in bulk and the ability to securely and easily receive content submitted by donors and contributors.

To prepare for these upcoming enhancements in PUT you will need to take action to modify your xml files to work in the new version of PUT – you can learn more below.

The following features are unchanged in PUT: 

  • the ability to select security tags for the whole package,
  • the ability to select the fixity algorithm and 
  • the use of the holding area or drag and drop to transfer content to PUT
  • the generic metadata fragment
  • adding fragments via the Manage Metadata option

 

Table of Contents

  • Editions
  • Preservica Versions
  • Introduction
    • Changes to .metadata
    • Changes to .xml
  • Fixity
  • Descriptive Metadata
  • Additional Resources
Did this topic help you find an answer to your question?

8 replies

Forum|alt.badge.img+6
  • Known Participant
  • 168 replies
  • January 19, 2023

Hello - Can I confirm that I should be uploading .opex files into my PUT tool as of today (19 Jan. 2023)? I’m using CE/Professional. Thanks for the confirmation.

 

----Kate s.


CX Team
Forum|alt.badge.img+4
  • Author
  • Community Manager
  • 9 replies
  • January 19, 2023

You can always confirm the version you have by going to Help and About,

Regards


Forum|alt.badge.img+6
  • Known Participant
  • 168 replies
  • January 19, 2023
Customer Experience wrote:

You can always confirm the version you have by going to Help and About,

Regards

Sorry, I’m confused about this reply. I’m asking to confirm that I should now be uploading .OPEX files, not .metadata files. I saw that today was the scheduled day of the change-over, and I want to confirm that happened. Are you asking me what version I have? It’s 6.6.1. Thanks! Sorry for the confusion.

Kate


CX Team
Forum|alt.badge.img+4
  • Author
  • Community Manager
  • 9 replies
  • January 19, 2023

Hi

So if you are v6.6.1, then you yes you need to use .opex format for the metadata

For anyone else reading this, all the changes in PUT in v6.6.1 are summarised here,

Wendy
 

https://community.preservica.com/preservica-editions-88/preparation-and-upload-tool-put-improvements-from-version-6-6-1-1820

 


Forum|alt.badge.img
  • New Participant
  • 3 replies
  • February 2, 2023

When updating my metadata files to .opex instead of .metadata, do I also need to update my schema management documents (XSD, XML, and XSLT files)? If so what changes do I need to make to the schema management documents to account for OPEX? 


Halley Grogan
Preservica Employee
Forum|alt.badge.img+4
  • Preservica Employee
  • 49 replies
  • February 2, 2023

@jwachtel - your schema management documents (XSD, XML and XSLT files) can remain as is in your system. No need to update. 


Forum|alt.badge.img+1
  • Known Participant
  • 11 replies
  • February 6, 2023

I’m getting a validation error and I cannot figure out why. Do I put in a ticket for it or is there another help document I should be looking at first?


Halley Grogan
Preservica Employee
Forum|alt.badge.img+4
  • Preservica Employee
  • 49 replies
  • February 7, 2023

@JillianS - please raise a support ticket for this issue and if possible, include a screenshot of the validation error in PUT.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings