DRAFT / Notes to self as going through process, will update/revise/beautify for web later (starting with July update)

When SFX sends out a notice on the SFX-DISCUSS list that an update is ready:

  • Jen forwards the notice email to edit-sfx, with note that she will/has download(ed) the full release notes from the SFX documentation portal into the R:/SFX/Documentation/Release Notes folder; and points any news of interest.
  • Jen downloads the release notes

When Rich announces that the update has been done:

Download / save text files

  • added
    •  object portfolio
    • target
    • interface [don't need to look at this - stand-alone interfaces are also targets and are repeated on the Target list]
  • changed
    • target
    • interface [don't need to look at this - stand-alone interfaces are also targets and are repeated on the Target list]
  • not changed
    • target service
    • object portfolio
  • deleted
    • [none for july]
  • not deleted
    • object portfolio

what to do with each report? open each in excel

detail procedure for each kind of report:

NOT CHANGED

Target Service 

look at ACTIVE targets first

look at first column: Suggested change which notes what field was not changed

example: Suggested change (not implemented):The following columns were not updated due to localizations (suggested values):PARSE_PARAM

look at column noted above; the data in that field is what is in SFX now - it may or may not be what should be there (because was already updated locally)

how to find out what it should be:

1. Call up target service window in SFX

2. Look in the release notes (PDF or spreadsheet, whichever is easier) - find the target and what was changed.

3. For target service, the change is usually the PARSER or the PARSE_PARAM -- compare the two sources.

4. if they are the same, no action needed. if they are not, copy what is in the release notes and paste into the SFX window.

5. check a title or two to make sure the change works

6. you may need to update something in U/P fields; consult the TARGET Configuration document for help.

when done, delete the file from the R: drive

Object Portfolio

look at ACTIVE titles first

check Suggested Change column

look at column not changed; what's there may be old or locally updated information

unfortunately, can't tell from release notes what the new information (e.g. updated PARSE_PARAM) should be.

what to do:

1. test title to see if it works

2. if it does, no action needed

3. if not, ?? [check other portfolios in target; try to find via other portfolio, check Vera to see if info is updated there??]

when done, delete the file from the R: drive

NOT DELETED

Object Portfolio

usually object portfolios are not deleted when the record has been locally updated (threshold, different PARSER or PARSE_PARAM, etc.)

check only those that are ACTIVE

check to make sure the title does not connect as is

check Vera to see if it is there - will need to notify veradata if it needs to be hidden

remove local threshold, if there is one

de-activate the portfolio (and related target/service if it is the last one)

when done, delete the file from the R: drive

CHANGED

Target

These changes will affect the winnowing process for the monthly updates, so it is important to review and update the monthly report Template, and Targets at MIT file.

*For the Template, you only need to update changes made to the INTERNAL_NAME.

*For the Targets at MIT file, you need to update changes to the INTERNAL_NAME and/or PUBLIC_NAME.

Tip: don't sort - it could break the before/after pairs.

What to do:

1. Open the TARGET_changed file.

2. The changes are listed in pairs in the Event column: " After change" is followed by "Before change".  There is also a column indicating status (ACTIVE or INACTIVE).

3. In the Template file, locate the old name in either the CheckedTargets tab or the SkippedTargets tab.

4. Update only those whose INTERNAL_NAME has changed.

5. In the SFX Targets at MIT file, update internal and/or public name as indicated on the spreadsheet.

Save all the files. Delete the TARGET_changed file from the R: drive.

ADDED

Targets

This is important to review because it affects the winnowing process in the Template.

You need to determine whether the object portfolios [titles] in each new target needs to be or should be reviewed by DigAcq to add to the collection.

Some criteria to consider:

  • free access? - skip
  • books? - skip
  • non-subscribed aggregators - skip
  • AIP SCITATION, HIGHWIRE PRESS, INFORMAWORLD, INGENTA_CONNECT, JSTOR, METAPRESS -- keep
  • EBSCOHOST, ELSEVIER, GALEGROUP, HEIN_ONLINE, METAPRESS_SPRINGER, PROQUEST, SAGE, SPRINGER, SYNERGY, WILEY -- skip

If you know that a new target needs to be activated, do it now and update all the lists.

To process:

1. Sort the Target Internal Name column.

2. Evaluate the target; if need to be reviewed/checked, put "keep" in NOTES column; if not, put "skip" in NOTES column.

3. When all targets are labeled, sort the NOTES column.

4. Open the Template spreadsheet.

5. Copy all the "keep" targets (Internal_Name) in the TARGET_added file and paste to the bottom of the "CheckedTargets" tab in the Template file.

6. Add ACTIVE or INACTIVE to each target as appropriate.

7. Sort on the first column.

8. Copy all the "skip" targets (Internal_Name) in the TARGET_added file and paste to the bottom of the "SkippedTargets" tab in the Template file.

9. Add ACTIVE or INACTIVE to each target as appropriate.

10. Sort on the first column.

Save the files. Do _NOT_ delete the TARGET_added file. It will be used later for reporting the new targets to edit-sfx.


  • No labels
Write a comment…