Skip to content

Oai updates#263

Merged
ddavisgraphics merged 20 commits intodevelopfrom
OAIUpdates
Mar 10, 2017
Merged

Oai updates#263
ddavisgraphics merged 20 commits intodevelopfrom
OAIUpdates

Conversation

@MichaelRBond
Copy link
Copy Markdown
Contributor

@MichaelRBond MichaelRBond commented Mar 5, 2017 •
edited
Loading

As soon as this is deployed into production several things need to take place.

  • Database will need to be updated to accommodate new features.
  • Update script needs run to convert previous publicRelease field to current public release field.
  • All forms will need to be updated to remove the publicRelease field
  • All forms that had a publicRelease field will need to be updated to include the new Release to Public option
  • All forms that are updated to use the new release to public option will need to have the default selected appropriated (from the publicRelease field removed in a previous step)
  • All forms that will be exported to the OAI Application will need to be updated to have the form setting selected.
  • All forms that will be exported as OAI will need to have the fields selected that will be exported as OAI "oai release" set
  • All forms that are going to be exported to OAI should be updated, at the very least, with dublin core information. It would be best if all appropriate metadata shemas where included/updated
  • All export scripts will need to be updated for all the forms that use publicRelease, to use the new release to public feature-
  • Import scripts will need to be updated to update the URL using the MFCS API
  • The ACLs need to be appropriately so that the hydra servers have access to update the APIs.
  • -process_objects neeeds updated-
  • Be sure that all fields in all forms have "release to public" set correctly
  • Update stats pages to use new public release

@MichaelRBond
Fix variable typo
d9a4991
@MichaelRBond
nagios check
b4cf75e
@MichaelRBond
nagios check
6e02242
@MichaelRBond
nagios check
7333016
@MichaelRBond
Merge pull request #255 from wvulibraries/ExportingUpdate
3c7f25f 
nagios check
@MichaelRBond
Remove spaces around the joining of matadata standards
05ade23 
Spaces were incorrectly used in the concatination of the metadata standards information. This removes them on creation. 

It does not address the issue that there is already data saved incorrectly in production. WVU is not currently using the metadata information in production. 

To mitigate this issue the best course of action will be to open all the forms that have metadata standards defined and save them. This should save the data correctly and not require aditional modifications.
@MichaelRBond
Merge pull request #256 from wvulibraries/RemoveSpacesAroundMetadataS…
2ebeba3 
…tandards

Remove spaces around metadata standards
@MichaelRBond
Add objects::getByIDNO()
e0739b5 
Retrieve an object with its IDNO, instead of the system ObjectID
@MichaelRBond
Update ACL includes for the API
9001dcb
@MichaelRBond
API for adding a URL to an Object
fcd1a65 
This is provided so that import scripts for other systems ca update MFCS with regards to where the object is viewable by the public.
@MichaelRBond
Switched all methods in Objects class to use standard $engine call
2c197c1
@MichaelRBond
Added todo and place-holder file
112343e 
forms class file should be broken up. It is currently handling two distinct functions 

1. building and taking web form submissions 
1. handling everything about a "form" 

A place holder file has been created, called web_forms.php to support the refactoring
@MichaelRBond
Updated securityConcerns with clarifying information.
b0b5ef9
@MichaelRBond
Changed objects::getObjects() to honor ignoreCache
80b4f8a 
This is essential when getting all objects on systems with limited memory. Cache drastically speeds up many operations, but in some cases is not required.
@MichaelRBond
Add method to count all objects in the system.
c24ab96 
Accepts parameter to exclude metadata objects
@MichaelRBond
Add column to objects table for publicRelease of objects
5d821e1
@MichaelRBond
CLI Script to convert from previous way of defining publicRelease object
b21d690
@MichaelRBond
Add Release to Public to Object forms
66ef257 
1. Add ability to add a public release select box to object forms.
1. Add ability to set the default value of yes/no to public release select
1. add public release to the object create/update forms

Note: when this gets merged into master someone will have to update all of the forms and the export forms. Any form with "publicRelease" will need that removed from the form. 

Any exports that use public release will need to be updated.
@MichaelRBond
Ad OAI Release to individual fields.
bd0b034 
This is required because some fields may be tagged for public release, to a local repository, but should not be included in an OAI release. this could be the case, especially, if there are multiple digital object fields. The public release can be utilized to export all digital objects, but then be hidden from OAI and a single URL can be provided for the item.
@MichaelRBond
Display Public URLs on the object page, in a new tab.
a684672
@ddavisgraphics
Copy link
Copy Markdown
Contributor

ddavisgraphics commented Mar 6, 2017

Lets talk about this on Thursday.

@ddavisgraphics
Copy link
Copy Markdown
Contributor

ddavisgraphics commented Mar 10, 2017

I'm going to merge this in, but we need to answer the order of some of these items. I'm assuming that this will also be tested on MFCS dev before going to the production area.

@ddavisgraphics ddavisgraphics merged commit 6aeffa4 into develop Mar 10, 2017
@ddavisgraphics ddavisgraphics deleted the OAIUpdates branch May 15, 2017 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@ddavisgraphics ddavisgraphics

@jmm0177 jmm0177

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@MichaelRBond @ddavisgraphics @jmm0177