Forgot password? | Forgot username? | Register
  • Index
  • » Users
  • » Kate Webbink
  • » Profile

Posts

Posts

Hey there,
Does anyone know of a way to batch import Multimedia records where the main "Multimedia" is a reference to a directory path on a server? 
e.g., "\\servername\folder1"

Seems similar to "how to batch import URLs" -- but I didn't have any luck when I set up a batch import CSV that included these columns:
- Multimedia - with a path to a folder on the server for each record
- MulDocumentType - with all records' values set to "U"

I also tried an "R" (for "Reference") in MulDocumentType, but in both cases, got errors saying "Cannot open file \\servername\foldername" and "Cannot save document 'foldername' on server."

Manually adding these paths to a record works fine directly in the Multimedia module -- by going to Multimedia -> Add -> Reference, and pasting the path to a folder.

& as far as why on earth we would do this:  We're setting up Multimedia records for folders of raw video footage. We aren't importing the footage itself partly because of its overall size, and partly because cataloging the footage logs as Multimedia records suffices.

Many thanks for any help,
Kate

21-Jan-16 10:41:32
Storage of 3D data and formats in EMu
Forum: Multimedia

Hi Ellen,
We're storing CT Scans in EMu/Multimedia currently, with a preview video visible on the main Multimedia tab, and raw scan files zipped and attached on the Supplementary tab of the same record. 

A lot of our raw scan files are BMP or DICOM image sequences--too many &/or too big for us to put into EMu raw, so a zipped archive was the simplest way we could keep a scan's file structure together.  Since that zip file won't give users a clear view of what was scanned, we also converted the raw image sequence into an mp4 video.  (Software like Adobe Media Encoder or MPEG Streamclip should be able to treat a folder of images as a video file & convert to different formats)

Not sure if EMu [or ImageMagick?] will have a way to accommodate 3d-media viewing down the road...For now, one downside with our approach is that the metadata from raw scan files is still a bit hidden/hard to search for when zipped & on the Supplementary tab.   If you need to protect access to any full raw datasets, though, this is one way to do it...Good luck--Keen to hear what you end up doing!
-kate

Thanks for the update, Giselle! 

Not much progress here, but we tested "iconv" (along with Access & Open/LibreOffice) for converting small batches of data reported or imported as CSVs.  Those solve some of the problems we ran into with opening/handling data with special characters in Excel.  Otherwise, though, we still don't have a more efficient method of converting datasets or spot-checking/globally replacing whichever characters would need it.

Hope Axiell can work something out, or offer advice/support for conversions.

----(and in case it's of use for anyone:
To use iconv to encode Excel csv's as UTF8:
- instal iconv (consider dbaportal.eu/2012/10/24/iconv-for-windows/)
- In a command prompt:
1) cd path/to/unconverted/CSVs:
2) iconv -f CP1252 -t UTF-8 infile > outfile

(use an excel-generated csv for "infile" & give it a new "outfile" name)
(also: beware of opening the "outfile" with Excel; depending on the version, that can unintentionally mangle UTF8 characters & convert it right back to Latin1)

Hi Giselle--Many thanks for the details.

Have you been able to test-run a CSV report of data in EMu that includes Chinese/other Asian-language characters? 

For us, CSV's that come out of EMu replace Arabic script with what looks like a utf reference, e.g.:

\x{063a}\x{0631}\x{0628} \x{0643}\x{064a}\x{0634}

...In which case, maybe the CSV's that EMu is able to report might still be Latin-1 (or at least not UTF8) encoded?

It also looks like those 3 points you listed are in fact all issues in our test environment.

- searches are case sensitive for special characters
- sorts don't follow a "mapped to Latin character" order
- when importing data, any special characters/accented letters in a csv encoded with Latin-1 character set turn into "?" in EMu records

..definitely curious to know whether/when any fixes or workarounds are available. (Currently testing/comparing workflows involving Excel, Libre Office, specifying UTF8 in the CSV formatting versus not, etc)

Thanks again
-Kate

Hi Giselle & all,

Apologies--this isn't much of an answer, but more of a "we're in the same boat," about to switch from Latin-1 to UTF-8 to accommodate datasets with Arabic text.  Likewise, just wondering if others out there have noticed (& resolved) any issues with character set transitions. 

So far, we haven't found issues in our test environment which just switched to UTF-8, but also not exactly sure what to check for...

Thanks for any wisdom & take care!
-Kate

Hi there,

We're using Narratives to put together content for a website, and are at the stage of copy-editing and attaching Catalog/Multimedia/Taxonomy/Events records to our Narratives.

Beyond the EMu help docs, does anyone have workflow wisdom or recent examples of Narratives-as-content-management to share? 


Many thanks for any info!
-kate

07-May-14 07:38:45
Working on color-coded Page Views but having xslt trouble
Category: Using EMu

Hi Keith,
That works like a charm over here--Many thanks!  And apologies for the belated reply!

I'm realizing that multi-word values sharing the same first word are colored by the first word.  Probably means we should avoid spaces in values for that field, but so far that actually helps to color code related values...Happy accident!

Again, many thanks for the solution + explanation!
-Kate

20-Mar-14 02:29:21
Working on color-coded Page Views but having xslt trouble
Category: Using EMu

Many thanks again, Keith!

I tried one other thing in the page view properties, and the department color-coding seems to work now, after changing one setting to treat the "SecDepartment_tab" as text:  Report--> Properties--> "Fields" tab--> highlight the department field & click "Table as Text" button)

Not sure if that's a good fix, though, so if you're up for taking a look, I put the xml on google drive (original + fixed xml, along with the corresponding html if it helps):

http://drive.google.com/file/d/0B9ciPt0 … jNDZVYtaVE
(forum wasn't accepting them as attachments here)

If you have any trouble accessing them, let me know, and again, major thanks for your help.
-kate

15-Mar-14 10:02:53
Working on color-coded Page Views but having xslt trouble
Category: Using EMu

Hi Keith,
Many thanks for the wisdom! (and for braving the eye-searing colors!)
The explanation makes sense, but I haven't been able to get it to work yet.  I think our department field "SecDepartment_tab" is a table (or at least not an atom), so I'm not sure how the syntax needs to change in order to reference it.  (Just changing the name of the ref from your example didn't work.) 

If interested, we've almost gotten something else to work:  Instead of just adding a css class for each condition (which is probably cleaner & more specific), we used a "when" test in the Atom template to color code for Event Type (we have "Video," "Exhibit - Temporary," etc). 

Downsides are that the code is messier, and if any other field values ever happen to match the Event Type's value, they'd probably get color-coded, too.  (I also couldn't get this method to work for our departments.)

...So I'll keep trying to work out the css-approach you recommended...If you have further advice, I am all ears.  Again, thank you!
-kate

What we currently have is attached (in full) and pasted below (in part)
color-event-type.txt
color-coded-dpt.txt
...each attached .txt is an .xsl, without the header:  <?xml version="1.0" encoding="ISO-8859-1" ?>


   <!--
            Atom template
     -->
    <xsl:template match="atom">
        <xsl:variable name="column" select="document('')/*/emu:column[@name=current()/@name]" />
    <xsl:choose>
        <xsl:when test=".= 'Botany'">
           <tr class="atomvalue">
                <td class="atomprompt">
                    <xsl:call-template name="prompt">
                        <xsl:with-param name="column" select="$column" />
                    </xsl:call-template>
                </td>
                <td class="atomvalue" bgcolor="#b2D487">
                  <xsl:value-of select="." />
                </td>
            </tr>
        </xsl:when>
        <xsl:when test=".='Zoology'">
          <tr class="atomvalue">
                <td class="atomprompt">
                    <xsl:call-template name="prompt">
                        <xsl:with-param name="column" select="$column" />
                    </xsl:call-template>
                </td>
                <td class="atomvalue" bgcolor="#d04123">
                  <xsl:value-of select="." />
                </td>
            </tr>
</xsl:when>
        <xsl:otherwise>
          <tr class="atomvalue">
                <td class="atomprompt">
                    <xsl:call-template name="prompt">
                        <xsl:with-param name="column" select="$column" />
                    </xsl:call-template>
                </td>
                <td class="atomvalue">
                    <xsl:value-of select="." />
                </td>
            </tr>
    </xsl:otherwise>
      </xsl:choose>
    </xsl:template>

26-Feb-14 05:38:27
Working on color-coded Page Views but having xslt trouble
Category: Using EMu

Hi there,
I'm trying to make a page view that changes color depending on values in certain fields--e.g., the department attached to an event record.  (For example, show a red background or red somewhere for event records when the "SecDepartment_tab" field is "Zoology;" show green if that field is "Botany," etc.)

So far, by using an "xsl: when" test in the "data template" section of the standard page view xslt stylesheet, we've managed to set rows to show [scary] colors, but no luck getting the color to change based on the fields/values we're trying to specify...I've been trying different ways of specifying the field, and trying other sections of the stylesheet in case the "data template" isn't the place for this.

In the meantime, though, does anyone out there have wisdom to share on conditionally formatting page views?

If it helps, a chunk of our xsl is below (possibly messy, but I'm happy to send a clearer copy of the actual xsl file we're attaching to the page view if anyone wants a look.)
Thanks for any help!
-Kate

---------------------beginning of our xsl chunk---------------------
    <!--
            Data template
     -->
    <xsl:template name="data">
           <xsl:variable name="column" select="document('')/*/emu:column[@name=current()/@name]" />
      <xsl:choose>
        <xsl:when test="not(atom[@name='EveTypeOfEvent'] = 'Video')">
<tr class="values">
            <td class="values" bgcolor="#00ffff">
                <table border="0" class="data" id="datatable">
                    <xsl:apply-templates select="*" />
                </table>
            </td>
        </tr>
        </xsl:when>
        <xsl:when test="not(atom[@name='EveTypeOfEvent'] = 'Exhibit - Temporary')">
        </xsl:when>
        <xsl:when test="not(atom[@name='EveTypeOfEvent'] = 'Technology')">
        </xsl:when>
        <xsl:otherwise>
<tr class="values">
            <td class="values" bgcolor="#ff33ff">
                <table border="0" class="data" id="datatable">
                    <xsl:apply-templates select="*" />
                </table>
            </td>
        </tr>
            </xsl:otherwise>
      </xsl:choose>
      <!--
<tr class="values">
            <td class="values">
                <table border="0" class="data" id="datatable">
                    <xsl:apply-templates select="*" />
                </table>
            </td>
        </tr>
        -->
    </xsl:template>

---------------------end of xsl chunk---------------------

  • Index
  • » Users
  • » Kate Webbink
  • » Profile

Board Info

Board Stats
 
Total Topics:
601
Total Polls:
0
Total Posts:
1362
User Info
 
Total Users:
830
Newest User:
Hillery
Members Online:
1
Guests Online:
95