Titling Best Practices

Hello
Working with AE and Premier I am starting to wonder what the best way of titling my videos in Premier is.
When I use AE I can get all sorts of fancy results but sometimes the quality of the edges of the fonts and stuff looks jaggy.
My project is video from a consumer camera, a Panasonic PV-GS150 to be exact, and although it is a good camera the video isnt super quality.
After I capture my footage in Premier I get it laid out and then I use AE to create Compositions that I import and drop into the video project in Premier and place it over the footage to create my titles. I have had differing success. Sometimes it is super crisp and sometimes it shows a case of the jaggies.
Could this be caused by interlacing or the type of scan that I set the render of the video too? I have been using progressive scan lately and I think the video quality of some of my latest projects have been good.
Being a perfectionist I would like to know if there is something I am doing wrong. Is there a setting that would cause a little jaggyness, or some process that I could be doing different?
I was thinking about taking the section of video where I want my titles and putting it in the AE project and then putting the AE comp into the timeline in premier in place of where I want the titles to go.
What is the best way?

Have you read the
"Best practices for creating text and vector graphics for video" section of After Effects CS3 Help on the Web?
If you don't feel like clicking, here's the body of that document:
"Text that looks good on your computer screen as you are creating it can sometimes look bad when viewed in a final output movie. These differences can arise from the device used to view the movie or from the compression scheme used to encode the movie. The same is true for other vector graphics, such as shapes in shape layers. Keep the following in mind as you create and animate text and vector graphics for video:
* You should always preview your movie on the same sort of device that your audience will use to view it, such as an NTSC video monitor. (See Preview on an external video monitor.)
* Avoid sharp color transitions, especially from one highly saturated color to its complementary color. Sharp color transitions are difficult for many compression schemessuch as those used by MPEG and JPEG standardsto encode. This can cause visual noise near sharp transitions. For analog television, the same sharp transitions can cause spikes outside the allowed range for the signal, also causing noise.
* When text will be over moving images, make sure that the text has a contrasting border (such as a glow or a stroke) so that the text is still readable when something the same color as the fill passes behind the text.
* Avoid thin horizontal elements, which can vanish from the frame if they happen to be on an even scan line during an odd field, or vice versa. The height of the horizontal bar in a capital H, for example, should be three pixels or greater. You can thicken horizontal elements by increasing font size, using a bold (or faux bold) style, or applying a stroke. (See Formatting characters.)
* When animating text to move verticallyfor scrolling credits, for examplemove the text vertically at a rate in pixels per second that is an even multiple of the field rate for the interlaced video format. This prevents a kind of twitter that can come from the text movement being out of phase with the scan lines. For NTSC, good values include 0, 119.88, and 239.76 pixels per second; for PAL, good values include 0, 100, and 200 pixels per second.
Apply the Autoscroll - Vertical animation preset in the Behaviors category to quickly create a vertical text crawl.
Fortunately, many problems with text in video and compressed movie formats can be solved with one simple technique: Apply Fast Blur to the text layer, with a Blurriness setting between 1 and 2. A slight blur can soften color transitions and cause thin horizontal elements to expand."

Similar Messages

  • Best Practice(s) for Laptop in Field, Server at Home? (Lightroom 3.3)

    Hi all!
    I just downloaded the 30-day evaluation of Lightroom, now trying to get up to speed. My first task is to get a handle on where the files (photos, catalogs, etc.) should go, and how to manage archiving and backups.
    I found a three-year-old thread titled "Best Practice for Laptop in Field, Server at Home" and that describes my situation, but since that thread is three years old, I thought I should ask again for Lightroom 3.3.
    I tend to travel with my laptop, and I'd like to be able to import and adjust photos on the road. But when I get back home, I'd like to be able to move selected photos (or potentially all of them, including whatever adjustments I've made) over to the server on my home network.
    I gather I can't keep a catalog on the server, so I gather I'll need two Lightroom catalogs on the laptop: one for pictures that I import to the laptop, and another for pictures on the home server -- is that right so far?
    If so, what's the best procedure for moving some/all photos from the "on the laptop catalog" to the "on the server catalog" -- obviously, such that I maintain adjustments?
    Thanks kindly!  -Scott

    Hi TurnstyleNYC,
    Yes, I think we have the same set-up.
    I only need 1 LR-catalog, and that is on the laptop.
    It points to the images wherever they are stored: initially on the laptop, later on I move some of them (once I am am fairly done with developing) within LR per drag&drop onto the network storage. Then the catalog on the laptop always knows they are there.
    I can still continue to work on the images on the network storage (slightly slower than on laptop's hard drive) if I still wish to.
    While travelling, I can also work on metadata / keywording, although without access to my home network the images themselves are offline for develop work.
    2 separate catalogs would be very inconvenient, as I would always have to remember if I have some images already moved. No collections would be possible of images including some on the laptop, some on the network.
    Remember: a LR catalog is just a database with entries about images and the pointer to their storage location.
    You can open only 1 DB of this sort at a time.
    There is no technical reason for limiting a LR-catalog - I have read of people with several hundert thousand images within one.
    The only really ever growing part on my laptop with this setup is the previews folder "<catalog name> Previews.lrdata". I render standard previews so that I can do most of the work for offline-images while travelling.
    The catalog itsself "<catalog name>.lrcat" grows much slower. It is now 630 MB for 60'000+ images, whereas previews folder is 64 GB.
    So yes, I dedicate quite a junk of my laptop hard disk to that. I could define "standard"-previews somewhat smaller, fitting to the laptop's screen resolution, but then when working at home with a bigger external monitor LR would load all the time for the delta size, which is why I have defined standard-preview-size for my external monitor. It may turn out to be the weakness of my setup long-term.
    That is all what is needed in terms of Lightroom setup.
    What you need additionally to cover potential failure of drives is no matter of LR, but *usual common backup sense* along the question "what can be recreated after failure, if so by what effort?" Therefore I do not backup the previews, but very thoroughly the images themselves as well as the catalog/catalog backups, and for convenience my LR presets.
    Message was edited by: Cornelia-I: sorry, initially I had written "1:1-previews", but "standard previews" is correct.

  • New Best Practice for Titles and Lower Thirds?

    Hi everyone,
    In the days of overscanned CRT television broadcasts, the classic Title Safe restrictions and the use of larger, thicker fonts made a lot of sense. These practices are described in numerous references and forum posts.
    Nowadays, much video content will never be broadcast, CRTs are disappearing, and it's easy to post HD video on places like YouTube and Vimeo. As a result, we often see lower thirds and other text really close to the edge of the frame, as well as widespread use of thin (not bold) fonts. Even major broadcast networks are going in this direction.
    So my question is, what are the new standards? How would you define contemporary best practice?
    Thanks for your thoughtful replies!
    Les

    stuckfootage wrote:
    I wish I had a basket of green stars...
    Quoted for stonedposting.
    Bzzzz, crackle..."Discovery One, what is that object?
    Bzz bzz."Not sure, Houston, it looks like a basket...." bzzz
    Crackle...."A bas...zzz.. ket??"
    Bzzz. "My God, It's full of stars!" bzz...crackle.
    Peeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee eeeeeeeeeep!

  • Best practices for TOC, versus PROJ title, filename

    I am seeking "best practice" help from the forum. Say a TOC
    is to have numbers as part of the organization, 1,2,3...and topics
    will be sub-numbered (as in 1.1, 1.2.1, 1.2.2, etc). I am not aware
    of any way to automatically manage this, they must be explicitly
    typed in the TOC editor.
    I have heard some say that the "view" in the Project should
    mirror the view in the TOC. That would imply that folder
    organization, filenames and titles would be in sync with the TOC,
    and also include the section/chapter numbering.
    If you have to make a change and resequence things, or insert
    a new chapter between 2 and 3 then there is a LOT of work to do.
    I am leaning in the direction of having filenames and titles
    be separate from the TOC structure, and not use Field[title] in the
    documents to simplify the update process. This would also simplify
    updating links within the documents.
    However, I am still pretty new with Robo and don't have the
    seasoning some of you have with long term effects of particular
    organization.
    Any help, or best practices that can be shared?
    Thanks!
    Don

    Thanks for your input Colum,
    I am actually considering the opposite of your comment - to
    have numbering in the TOC but NOT with the Project folders. I
    consider the TOC much more volatile and flexible than the folder
    structure. As long as one knows what goes with what. So the good
    news is there is not a sacrosanct line drawn between the project
    names and structure and that in the TOC. This helps. If I have to
    resequence section 2 and section 5, I mainly just change the TOC. I
    would not have to move or rename any folders in the Project view.
    The other part, using the document title (in the topic
    properties) to automatically update the topic title in the text I
    like quite a bit and I think can make the case with my peers. That
    offers a lot of flexibility. As in the above mentioned
    resequencing, I would have to access the properties for each topic
    in the project folder that used to be in section 2, and edit the
    document title to reflect its new position in section 5 (and vice
    versa). That is pretty straightforward. I do NOT have to rename all
    those folders and files in the Project view.
    Thanks again for chiming in.
    Don

  • Best Practice: Dynamically changing Item-Level permissions?

    Hi all,
    Can you share your opinion on the best practice for Dynamically changing item permissions?
    For example, given this scenario:
    Item Creator can create an initial item.
    After item creator creates, the item becomes read-only for him. Other users can create, but they can only see their own entries (Created by).
    At any point in time, other users can be given Read access (or any other access) by an Administrator to a specific item.
    The item is then given edit permission to a Reviewer and Approver. Reviewers can only edit, and Approvers can only approve.
    After the item has been reviewed, the item becomes read-only to everyone.
    I read that there is only a specific number of unique permissions for a List / Library before performance issues start to set in. Given the requirements above, it looks like item-level permission is unavoidable.
    Do you have certain ideas how best to go with this?
    Thank you!

    Hi,
    According to your post, my understanding is that you wanted to change item level permission.
    There is no out of the box way to accomplish this with SharePoint.               
    You can create a custom permission level using Visual Studio to allow users to add & view items, but not edit permission.   
    Then create a group with the custom permission level. The users in this group would have the permission of create & add permission, but they could no edit the item.
    In the CodePlex, there is a custom workflow activities, but by default it only have four permission level:
    Full Control , Design ,Contribute and Read.
    You should also customize some permission levels for your scenario. 
    What’s more, when use the SharePoint 2013 designer, you should only use the 2010 platform to create the workflow using this activities,
    https://spdactivities.codeplex.com/wikipage?title=Grant%20Permission%20on%20Item
    Thanks & Regards,
    Jason
    Jason Guo
    TechNet Community Support

  • Best practices for setting up projects

    We recently adopted using Captivate for our WBT modules.
    As a former Flash and Director user, I can say it’s
    fast and does some great things. Doesn’t play so nice with
    others on different occasions, but I’m learning. This forum
    has been a great source for search and read on specific topics.
    I’m trying to understand best practices for using this
    product. We’ve had some problems with file size and
    incorporating audio and video into our projects. Fortunately, the
    forum has helped a lot with that. What I haven’t found a lot
    of information on is good or better ways to set up individual
    files, use multiple files and publish projects. We’ve decided
    to go the route of putting standalones on our Intranet. My gut says
    yuck, but for our situation I have yet to find a better way.
    My question for discussion, then is: what are some best
    practices for setting up individual files, using multiple files and
    publishing projects? Any references or input on this would be
    appreciated.

    Hi,
    Here are some of my suggestions:
    1) Set up a style guide for all your standard slides. Eg.
    Title slide, Index slide, chapter slide, end slide, screen capture,
    non-screen capture, quizzes etc. This makes life a lot easier.
    2) Create your own buttons and captions. The standard ones
    are pretty ordinary, and it's hard to get a slick looking style
    happening with the standard captions. They are pretty easy to
    create (search for add print button to learn how to create
    buttons). There should instructions on how to customise captions
    somewhere on this forum. Customising means that you can also use
    words, symbols, colours unique to your organisation.
    3) Google elearning providers. Most use captivate and will
    allow you to open samples or temporarily view selected modules.
    This will give you great insight on what not to do and some good
    ideas on what works well.
    4) Timings: Using the above research, I got others to
    complete the sample modules to get a feel for timings. The results
    were clear, 10 mins good, 15 mins okay, 20 mins kind of okay, 30
    mins bad, bad, bad. It's truly better to have a learner complete
    2-3 short modules in 30 mins than one big monster. The other
    benefit is that shorter files equal smaller size.
    5) Narration: It's best to narrate each slide individually
    (particularly for screen capture slides). You are more likely to
    get it right on the first take, it's easier to edit and you don't
    have to re-record the whole thing if you need to update it in
    future. To get a slicker effect, use at least two voices: one male,
    one female and use slightly different accents.
    6) Screen capture slides: If you are recording filling out
    long window based databse pages where the compulsory fields are
    marked (eg. with a red asterisk) - you don't need to show how to
    fill out every field. It's much easier for the learner (and you) to
    show how to fill out the first few fields, then fade the screen
    capture out, fade the end of the form in with the instructions on
    what to do next. This will reduce your file size. In one of my
    forms, this meant the removal of about 18 slides!
    7) Auto captions: they are verbose (eg. 'Click on Print
    Button' instead of 'Click Print'; 'Select the Print Preview item'
    instead of 'Select Print Preview'). You have to edit them.
    8) PC training syntax: Buttons and hyperlinks should normally
    be 'click'; selections from drop down boxes or file lists are
    normally 'select': Captivate sometimes mixes them up. Instructions
    should always be written in the correct order: eg. Good: Click
    'File', Select 'Print Preview'; Bad: Select 'Print Preview' from
    the 'File Menu'. Button names, hyperlinks, selections are normally
    written in bold
    9) Instruction syntax: should always be written in an active
    voice: eg. 'Click Options to open the printer menu' instead of
    'When the Options button is clicked on, the printer menu will open'
    10) Break all modules into chapters. Frame each chapter with
    a chapter slide. It's also a good idea to show the Index page
    before each chapter slide with a progress indicator (I use an
    animated arrow to flash next to the name of the next chapter), I
    use a start button rather a 'next' button for the start of each
    chapter. You should always have a module overview with the purpose
    of the course and a summary slide which states what was covered and
    they have complete the module.
    11) Put a transparent click button somewhere on each slide.
    Set the properties of the click box to take the learner back to the
    start of the current chapter by pressing F2. This allows them to
    jump back to the start of their chapter at any time. You can also
    do a similar thing on the index pages which jumps them to another
    chapter.
    12) Recording video capture: best to do it at normal speed
    and be concious of where your mouse is. Minimise your clicks. Most
    people (until they start working with captivate) are sloppy with
    their mouse and you end up with lots of unnecessarily slides that
    you have to delete out. The speed will default to how you recorded
    it and this will reduce the amount of time you spend on changing
    timings.
    13) Captions: My rule of thumb is minimum of 4 seconds - and
    longer depending on the amount of words. Eg. Click 'Print Preview'
    is 4 seconds, a paragraph is longer. If you creating knowledge
    based modules, make the timing long (eg. 2-3 minutes) and put in a
    next button so that the learner can click when they are ready.
    Also, narration means the slides will normally be slightly longer.
    14) Be creative: Capitvate is desk bound. There are some
    learners that just don't respond no matter how interactive
    Captivate can be. Incorporate non-captivate and desk free
    activities. Eg. As part of our OHS module, there is an activity
    where the learner has to print off the floor plan, and then wander
    around the floor marking on th emap key items such as: fire exits;
    first aid kit, broom and mop cupboard, stationary cupboard, etc.
    Good luck!

  • Best practice for setting or detecting screen size?

    Hi All,
    Trying to determine a best practice for setting or detecting the screen size. For playbook and iOS, I can set them. But for Android, the number of devices is too large so I'd rather detect. My first choice is to use the stage.stageHeight and stage.stageWidth. This works fine if I set my stage properties with standard meta data:
    [SWF(height="320", width="480", frameRate="64", backgroundColor="#010101")]
    However, if I use the application descriptor file to set the stage dimentions (as suggested by Christian Cantrell here http://www.adobe.com/devnet/flash/articles/authoring_for_multiple_screen_sizes.html)
    <initialWindow>
    <aspectRatio>landscape</aspectRatio>
    <autoOrients>false</autoOrients>
    <width>320</width>
    <height>480</height>
    <fullScreen>true</fullScreen>
    </initialWindow>
    Then the stage.stageHeight and stage.stageWidth are not the correct numbers when my main class is added to the stage. Sometime after the main class is added to the stage, then those numbers are fine. Is there an event I can wait for to know that the stage.stageHeight and stage.stageWidth are correct?
    Thanks in advance!

    Hi Lee,
    Thanks for the quick response! However, for some reason the heightPercent & widthPercent metadata tags are not working as expected for me.
    I have a wrapper class that I target for compiling, WagErgApplePhone.as where I've got my metadata
    [SWF(heightPercent="100%", widthPercent="100%", frameRate="64", backgroundColor="#010101")]
    sets some stage properties
    stage.quality=StageQuality.LOW;
    stage.scaleMode = StageScaleMode.NO_SCALE;
    stage.align = StageAlign.TOP_LEFT;
    and instantiates my main class
    var main:Main = new Main();
    addChild(main);
    my main class constructor even waits for the stage
    public function Main(){
    if (stage) init();
    else addEventListener(Event.ADDED_TO_STAGE, init);
    in my init function, stage.stageHeight traces out as 375 (expecting 320).
    i have a function which is called via a button press event by the user, and stage.stageHeight traces out correctly (320) there. that's what makes me think that if i wait long enough, i can get the correct stageHeight before init/drawing. but i'm not sure what event to listen for, or if there's another trick.
    if i use Capabilities.screenResolutionX and Capabilities.screenResolutionY the correct values are provided for mobile, but these values are not useful for the desktop and web version of the app. if there's no other solution, i'll execute different code depending on platform.
    again, for reference, my app descriptor:
    <initialWindow>
    <aspectRatio>landscape</aspectRatio>
    <autoOrients>false</autoOrients>
    <width>320</width>
    <height>480</height>
    <content>bin-iOS/WagErgApplePhone.swf</content>
    <title>WAG ERG</title>
    <fullScreen>true</fullScreen>
    <renderMode>cpu</renderMode>
    </initialWindow>
    looking forward to any other ideas to try out & thanks so much for your thoughts! if you want to really dig in, this is an opensource project at code.google.com/p/wag-erg/

  • Best practice - updating figure numbers in a file, possibly to sub-sub-chapters

    Hi,
    I'm a newbie trying to unlearn my InDesign mindset to work in FrameMaker. What is best practice for producing figure numbers to accompany diagrams throughout a document? A quick CTRL+F in the Framemaker 12 Help book doesn't seem to point me in a particular direction. Do diagrams need to be inserted into a table, where there is a cell for the image and a cell for the figure details in another? I've read that I should  use a letter and colon in the tag to keep it separate from other things that update, e.g. F: (then figure number descriptor). Is there anything else to be aware of, such as when resetting counts for chapters etc?
    Some details:
    Framemaker12.
    There are currently 116 chapters (aviation subjects) to make.
    Each of these chapters will be its own book in pdf form, some of these chapters run to over 1000 pages.
    Figure number ideally takes the form: "Figure (a number from one of the 1-116 chapters used) - figure number" e.g. "Figure 34 - 6." would be the the 6th image in the book 'chapter 34'.
    The figure number has to cross reference to explaining text, possibly a few pages away.
    These figures are required to update as content is added or removed.
    The (aviation) chapter is an individual book.
    H1 is the equivalent of the sub-chapter.
    H2 is the equivalent of the sub-sub-chapter.
    H3 is used in the body copy styling, but is not a required detail of the figure number.
    I'm thinking of making sub-chapters in to individual files. These will be more manageable on their own. They will then be combined in the correct order to form the book for one of these (1 of 116) subject chapters.
    Am I on the right track?
    Many thanks.
    Gary

    Hi,
    Many thanks for the link you provided. I have implemented your recommendation into my file. I have also read somewhere about sizing anchored frames to an imported graphic using 'esc' + 'm' + 'p'.
    What confuses me, coming from InDesign is being able to import these graphics at the size they were made ( WxH in mm at 300ppi) and keeping them anchored to a point in the text flow.
    I currently have 1 and 2 column master pages built. When I bring in a graphic my process is:
    insert a single cell table on the next space after current text > drop the title below the cell > give the title a 'figure' format. When I import a graphic it either tries to fit it in the current 2 column layout with only part of it showing in a box which is half the width of a single column!
    A current example: page 1 (2 column page) the text flows for 1.5 columns. At the end of the text I inserted a single cell table, then imported and image into the cell.
    Page 2 (2 column page) has the last line of page 1's text in the top left column.
    Page 3 (2 page column)  has the last 3 words of page 1 in its top left column.  The right column has the table in it with part of the image showing. The image has also bee distorted, like it's trying to fit. These columns are 14 cm wide, the cell is 2 cm wide at this point. I have tried to give cells for images 'wider' attributes using the object style designer but with no luck.
    Ideally I'm trying to make 2 versions. 1) an anchored frame that fits in a 1 column width on a 2 column width page. 2) An anchored frame that fits the full width of my landscape pages (minus some border dimension),  this full width frame should be created on a new proceeding page. I'd like to be able drop in images to suit these different frames with as much automation as possible.
    I notice many tutorials tell you how to do a given area of the program, but I haven't been able to find one that discusses workflow order. Do you import all text first, then add empty graphic boxes and/or tables throughout and then import images? I'm importing text from Word,  but the images are separate, having been vectored or cleaned up in Photoshop - they won't be imported from the same word file.
    many thanks

  • Best practice to implement different Xcelsius dashboard for different users

    I'm implementing an Xcelsius dashboard that requires to show each individual user with different content (e.g. When a user logins in, the dashboard shows her name and job title, her performance and her subordinate's performance).  I'm just wondering what's the best practice to implement scenario like this?  Thanks.

    Hi Thomas
    What you are looking at is "Row Level Security" within BusinessObjects and the options you have are determined by what type of data you are reporting off of (relational data, OLAP data, BW data, etc.)
    For instance, if you are using relational data with a Universe you could setup a database table with the BusinessObjects username to correspond with their e-mail address or other unique identifier. From there, you could add security to your universe using the @variable('BOUSER')
    That way, any objects created off of the universe (whether it is a Crystal Report, Web Intelligence, BI Web Service, QaaWS, LiveOffice, etc.) will filter the data based on this security model. So any Xcelsius dashboard based on this underlying data will also be filtered.
    And that is just one of the options you have, depending on your data source.

  • Multi-Language support in Discoverer? Best-Practice?

    Dear experts,
    wondering if there is a best practice to provide workbooks/EULs in different languages? Actually we use Business Objects (BO 5.xx) but want to switch to Discoverer. As BO also does not support multiple languages we use as a workaround the VB-interface to translate the text and labels in our reports and universes (EUL) regarding to particular label numbers. Is there some kind of similar interface for browsing/changing Discoverer EULs?
    Do you think the following could work:
    In the "genuine" EUL you specify a unique number to any attibute of an element and after each you start a kind of translation procedure generating two new EULs (e.g. EUL_EN (english) and EUL_DE (german)) with translated labels (Name and Headline attibute of an element).
    As far as I understood the structure of Discoverer's EULs, all attibutes are stored in the database, so it should be possible to find out, which holds the "Name" and which the "Headline" attribute...
    Got what I want?
    At least I need to understand the data model of the EULs...
    Regards,
    Ralf

    Hi Ralf,
    There are 2 types of translations you might want to do: the names and descriptions of your Business Areas,Folders and Items etc in the EUL and the labels and titles in the workbooks.
    To translate the Descriptions in the EUL the easiest approach will be to export the EUL into an .eex file or each component into a .eex file using a script. These .eex files are in fact XML files and the names and descriptions are attributes of the XML BA, folder and item elements. You can then translate these and then import the eex file(s) into a new EUL for the new language.
    Another approach to consider (especially if you are using Discoverer with Oracle Applications and your translations are already held in the database) is to create a language specific EUL. You will need to use the command line to do this and specify the EUL language when you create the EUL. Then import your EUL into the new language specific EUL and use the folder refresh to pick up the translated text from the database. You will probably need to write a EUL_TRIGGER$REFRESH_NEW_COLUMN to do this. If you are using the Business Intelligence views some translations may be done for you when you refresh. I think taking this approach will be a challenge.
    I am afraid there is no easy way to translate the labels and titles in the workbooks. You will have to manually open each workbook in the new EUL, translate the text and save it.
    Hope that helps,
    Rod West

  • Best Practice for Placing meta tags in HEAD of document

    Good afternoon,
    We are utilizing Oracle UCM's ability to dynamically generate pages based on page templates, region templates, and contributor data files that contributors may edit and publish. We have a specific need to include meta tags in the head section of each page that are custom to the data present in each contributor data file. Including the meta tags in the region template that pertains to a section of our website does not work, as it does not include a <head> section. Alternatively, I can not place the meta tags in the page template, as the data in each meta tag is specific to the metadata surrounding each contributor data file.
    My question is this: Is there a best practice, or Oracle-supported method of accomplishing this task? I have to believe there is some way to accomplish this, as the need for meta tags for social media sites and search engines is very common.
    Thank you very much for your time,
    Josh

    Thanks for the reply, Jiri.
    I believe that the answer is 'yes' to both of your questions above. I do have a question about the formatting of the meta tag itself, as my main question is how do I extract the needed information from a particular CDF so that it is displayed in the <head> section located in the page template.
    I have a Region Definition for the content section of my page with a 'Title' field, which a contributor can fill in, save, and create a Contributor Data File with their own specified title. Let's also say that my page template, which formats the entire page, looks like this (rough):
    <html>
      <head>
      <title>Web page</title>
      </head>
      <body>
      <!-- placeholder for header section -->
      <!-- placeholder for content section -->
      <!-- placeholder for footer section -->
      </body>
    </html>
    What would my <meta> tag look like for the following:
      <meta property="og:title" content="Title of the content section"/>
    Let's name our templates/definitions:
    Page Template: PT_META
    Region Template: RT_META
    Region Definition: RD_META
    Contributor Data File: CDF_META
    In other words, how do I extract the information included in the Contributor Data File (as well as its metadata) for use in the Page Template? Is there some sort of Idoc Script call that can be used?
    Thank you so much,
    Josh

  • Best Practices for Projects

    I have a Mac Pro and one very full drive, so I've purchased an external drive to back-up all of my files and a new internal drive as well. It may be important to note that the FCP projects I create aren't true video projects. It's pretty simple -- I use FCP to bring together recorded audio with still images, and add some motion in to create "movies". Each of my movies (around 30 so far), and their specific associated files (audio and project-specific images) reside in their own file folders. My trouble comes in that I also have a huge folder of purchased stock images which resides in a separate file folder. Each of my individual movies connect to several of these stock images that exists outside of the movie's folder.
    I'm stuck on what I should do. The purchased stock image folder is common to all of the movies. Over time it will continue to grow. What I think I need to do is move this folder off of my main working drive and onto another drive that can handle the load. I would like to move my completed movie projects either to a self-contained disk for future reference and edits if necessary. I have no idea how to proceed, but I need to, and quickly. Can anyone offer a best practice on how to set this up and and tips/tricks to avoid potential pitfalls in doing this?
    Thanks in advance for any and all assistance!

    Because I edit in a few locations with several external drives I try not to use "common folders" anymore. Just gets too difficult if I have footage spread over multiple drives.
    I normally create a project and save it to a "projects" folder on the system drive.
    I capture to the root of an external drive.... I do not create any folders for this, FCP will create the project specific folders for scratch and renders.
    I then create a project specific "elements" folder on my external "project elements" drive. Any graphics or titles or stills or music that I create or use on the project gets placed here. So if I had, as you do, "a huge folder of purchased stock images" I would copy the pics I need for the specific project to it's elements folder before importing them into FCP. In my case it's usually old footage that is common to various projects. This does, of course require more drive space, but anything that helps keep my disorganized brain more organized is worth it to me.
    When I want to archive projects I just copy the project file and it's "elements" folder to my archive drive. I delete the capture scratch and render folders for that project as they can be recaptured and re-rendered if the need arises.
    rh

  • What are the best practice to design Dashboard?

    Hi Friends,
    What are the best practice to design Dashboard?
    Thanks

    1) Use section name instead of Title View to name your report. This way sections can be collapsed and user can still see report name.
    2) Enable alternate coloring in tables and pivots for easy readablity and set table and pivot widths to 100% (for reports in dashboards) to reduce white space and achieve a more "professional look."
    3) Use column selectors and view selectors to reduce the width of reports and reduce the amount of columns user sees to a "practical minimum."

  • Facelets template best practices

    Hi,
    As I gain more experience in JSF, I am doing things a bit differently. When I first started I was binding all components to a backing bean and using the component binding in code for various things such as multi component validation. Later I used only value bindings, and had a lot of configuration in the template:
    <select id="country" jsfc="h:selectOneMenu" value="#{user.countryCode}" validator="#{someBackingBean.country_validate}" required="true" requiredMessage="#{theme_messages['field.country']} #{theme_messages['word.required']}">
        <f:selectItems value="#{someBackingBean.countryItems}"/>
    </select>I modified that example from real code, so it might make more sense to use a converter than a validator for a country code... But anyway, there is a lot of per component configuration in my templates. When I create multiple themes/skins, this stuff has to be duplicated. When I make changes to the application, all themes have to be updated.
    I think Wicket encourages you to bind all components to the "backing bean" and do your configuration in code. Your equivalent template would look something like this:
    <select id="country" jsfc="h:selectOneMenu" binding="#{someBackingBean.countryDropDown}">
        <f:selectItems value="#{someBackingBean.countryItems}"/>
    </select>You might even leave the f:selectItems out of the template. The only challenge I foresee with this is that using JSF APIs to resolve EL to add a validator, converter, action, or whatever else into the component from code is very verbose and difficult. I asked the JSF expert group to enhance the APIs to make it easier to do everything in code, but it did not make the JSF 2.0 spec. They will consider it in a future release: [JSF API Ticket 363|https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=363]
    Can anyone share their experiences with facelets template complexities and best practices they have learned? If you do most of your component configuration in code, how much of it do you allow in the template? Do you allow value bindings? The f:selectItems tag?
    Thanks,
    Ryan

    If you want full understand facelets , Install NetBeans6.1, install facelets plugin for it, here isa link
    http://armarz.ifolder.ru/9150024. if you want more about facelets read this book -
    http://armarz.ifolder.ru/8396066 .
    In net beans the first create web/facelets application, create facelets template, and client pages for it.
    here is a template example, it hase top, left and content, also in each part inserted one xhtml file for defaults views(logo, logout...)
    <html xmlns="http://www.w3.org/1999/xhtml"
          xmlns:ui="http://java.sun.com/jsf/facelets"
          xmlns:h="http://java.sun.com/jsf/html"
          xmlns:f="http://java.sun.com/jsf/core">
      <head>
        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
        <link href="/css/tableLayout.css" rel="stylesheet" type="text/css" />
        <link href="/css/index.css" rel="stylesheet" type="text/css" />
        <title>My Template</title>
      </head>
      <body>
        <table cellpadding="0"  cellspacing="0" border="0" width="100%">
          <tr>
            <td id="top" valign="top" align="left" colspan="2" >
              <ui:insert name="top"></ui:insert>
              <ui:include src="top.xhtml"></ui:include>         
            </td>
          </tr>
          <tr>
            <h:panelGroup rendered ="#{,,;,;,;,;,;,;l}">                 
              <td id="left" valign="top" align="left" width="150px">
                <ui:insert name="left"></ui:insert>
                <ui:include src="left.xhtml"></ui:include>           
              </td>
            </h:panelGroup>
            <h:panelGroup rendered ="#{kjkjkjkjkjkkk}">                 
              <td>
                <table width="150px" cellpadding="0" cellspacing="0" border="0">
                  <tr>
                    <td>
                      <f:verbatim> </f:verbatim>
                    </td>
                  </tr>
                </table>
              </td>
            </h:panelGroup>
            <td id="content" valign="top" align="left">
              <ui:insert name="content"></ui:insert>
              <ui:include src="content.xhtml"></ui:include>
            </td>
          </tr>
        </table>
      </body>
    </html>And here is a client page.
    <ui:composition xmlns="http://www.w3.org/1999/xhtml"
                    xmlns:ui="http://java.sun.com/jsf/facelets"
                    xmlns:h="http://java.sun.com/jsf/html"
                    xmlns:f="http://java.sun.com/jsf/core"
                    xmlns:c="http://java.sun.com/jsp/jstl/core"
                    template="/layout/main.xhtml">////refer to main.xhtml template
      <ui:define name="content">
        <f:view>
          <h:form id ="login">
            <table width="200" border="0" cellpadding="0" cellspacing="0">
                <tr>
                  <td align="left" colspan="2" class="red" style="padding:0 0 5px 0" >                                               
                  </td>
                </tr>
                <tr>
                  <td class="form_text">
                    <h:outputText styleclass="form_text" value="#{bean.username}" />
                  </td>
                  <td>
                    <h:inputText styleClass="input_text" id="loginname" value="#{Login.username}" required ="true"
                                 requiredMessage="#{log.required}">                  
                    </h:inputText>
                  </td>
                </tr>
                <tr>
                  <td></td>
                  <td><h:message id="error" for="loginname" styleClass="validate" /></td>           
                </tr>
                <tr>
                  <td class="form_text">
                    <h:outputText styleclass="form_text" value="#{bean.pass}" />
                  </td>
                  <td >
                    <h:inputSecret styleClass="input_text" id="password" value="#{Login.password}" required ="true"
                                   requiredMessage="#{log.passlen}">                      
                    </h:inputSecret>
                  </td>
                </tr>
                <tr>
                  <td></td>
                  <td><h:message id="fail" for="password" styleClass="validate" /></td>           
                </tr>
                <tr>
                  <td>
                    <f:verbatim> </f:verbatim>
                  </td>
                </tr>           
                <tr>
                  <td></td>
                  <td align="right">
                    <h:commandButton styleClass="submit" style="float:right;" value="#{bean.login}" action="#{Login.loggedIn}"  >
                    </h:commandButton>
                  </td>
                </tr>
              </h:panelGroup>
            </table>
          </h:form>
        </f:view>
      </ui:define>
    </ui:composition>is this useful?:)

  • Azure Search Best Practice

    I have a few questions regarding best practices for implementing Azure Search, I am working on loading Titles and Usernames into Azure Search with a unique ID as key, search would be on various matching words in Titles or Usernames:
    - Is there a detailed article or whitepaper that discusses best practice?
    - Should we always use filter instead of search to improve response time?
    - I don't know how things work under the hood, is it possible to turn off certain features; for example, scoring profiles, to improve response time?
    - Can i run a load test on GET queries?  How many different GET queries?  Does the same query get cached?
    - I have setup an indexer with a AzureSQL data source with a data change policy against a DateModified column in the table.  This indexer runs every 5 minutes.  I'd imagine an index is necessary on this column in the SQL table?  Also, when
    the indexer runs, does it check all documents in the search index against the data source?
    Thanks in advance,
    Ken

    We don't have an end-to-end whitepaper that covers all of this yet. Here are notes on your specific questions, feel free to add more questions as details come up:
    Filter vs search: in general, more selective queries (where the combination of filter + search matches less documents of the overall index) will run faster since we need to score and sort less documents. Whether you choose filter vs search: if you want
    an exact boolean predicate then use a filter; if you want soft search criteria (with linguistics and such applied to it) then use search.
    Scoring profiles are off by default. They only kick in if you create a scoring profile in the index explicitly and either reference it in queries or mark it as default. With no scoring profiles present, scoring of documents is based on the properties of
    the search text and document text.
    Yes, you can do your perf testing using GET for search requests. While the same query doesn't get cached the underlying data ends up being warmer. A good pattern is to have a bunch of keywords and have your test create different searches with 2-3 words each
    (or whatever is typical in your scenario) based on those keywords.
    For the SQL table question, yes, it's better if you have an index in the column you use as high-watermark so SQL doesn't need to do a table scan each time the indexer runs. The larger the table the more important this is.
    This posting is provided "AS IS" with no warranties, and confers no rights.

Maybe you are looking for