Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: updated metadata from database of record is not synced to the interface #95

Open
kellyannewithane opened this issue Aug 24, 2018 · 8 comments

Comments

@kellyannewithane
Copy link
Collaborator

From user stories (processing archivist, round 2)

-As a processing Archivist, I want to update the descriptive metadata for a Collection or Folder from the database of record (currently TMS – this might be worth waiting on until CCA has a proper archival management system).

@jraddaoui
Copy link
Collaborator

We've developed interactions with the TMS API (in this PHP class). In Binder, the TMS metadata is automatically updated in an asynchronous task when a resource is visited and its TMSObject.LastModifiedCheckDate has changed from the last update. It can also be updated for the whole collection using a programed task.

This will require further analysis after knowing their management system and its API specifications. In this application, most of the metadata for Collections and Folders is Dublin Core, so we'll need to create a mapping to TMS objects and add new fields to the current models in this application.

@jraddaoui
Copy link
Collaborator

Hi @stefanabreitwieser, I'd need more information about the management system, its API specifications and how its metadata should map to this application models.

@stefanabreitwieser
Copy link
Collaborator

I think @marcbouchercca can answer the more technical aspects of this question for you. In the meantime, I'm putting together a TMS-Archivematica metadata crosswalk and will send it along when it's ready.

@marcboucher
Copy link

Hello, when you say "management system", you mean TMS?

@jraddaoui
Copy link
Collaborator

Hi @marcbouchercca!

I didn't want to fully asume it's going to be the TMS, from this issue description: "this might be worth waiting on until CCA has a proper archival management system". Also, Justin mentioned that it could be an intermediate application.

@stefanabreitwieser
Copy link
Collaborator

Yes, TMS -- the time-frame for replacing TMS has been extended since Tim first drafted the plan. We'll definitely need something with TMS compatibility in interim. Thanks!

@stefanabreitwieser
Copy link
Collaborator

Archivematica-TMS_crosswalk_final.docx
And here's the TMS-Archivematica crosswalk on the Collection and Folder levels -- it also maps the TMS fields to their related SQL tables. Let me know if you need any additional information!

@jraddaoui
Copy link
Collaborator

Thanks @stefanabreitwieser,

That helps to know that there is not too much to map between both applications. But, without knowing something about the API specifications this is still hard to estimate. Considering that such an API exists, that it will be accessible by this application and that a relation can be made between this application resources and the ones from the TMS; as a rough ballpark, this could go between 50 and 100 hours.

@jraddaoui jraddaoui added post-beta and removed round2 labels Sep 3, 2018
@jraddaoui jraddaoui removed their assignment Sep 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants